Hi Rob, Note that for Commons Daemon we do want to deploy the bin zip that contains the Windows DLL/EXEs.
Some folks, like me, depend on it in order to include the Windows EXE/DLLs in builds. Gary On Sat, Dec 2, 2017 at 2:06 PM, Rob Tompkins <[email protected]> wrote: > Hello all, > > In my work on the [build-plugin], I’ve come across the following mechanism > to prevent the [maven-assembly-plugin] from deploying the artifacts to > nexus. If in the configuration section of the plugin, you put > “<attach>false</attach>” the archives that the [maven-assembly-plugin] > creates will not get pushed up to nexus. For example I have locally in > [text] the following: > > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptors> > <descriptor>src/assembly/bin.xml</descriptor> > <descriptor>src/assembly/src.xml</descriptor> > </descriptors> > <tarLongFileMode>gnu</tarLongFileMode> > <attach>false</attach> > </configuration> > </plugin> > > and with that, using "-Ptest-deploy" profile, the archives aren’t pushed > to "./target/deploy”. > > As previously stated, my plan is to streamline the release process > considerably with java updates to the build plugin, but for the time being, > this should be helpful. > > Cheers, > -Rob > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
