Re: What does the TODO refering to a "jarjar" format in the maven-assembly-plugin jar-with-dependencies example mean?
Thanks for the insight! I guess we'll have to hope for more info from Brett. Since the TODO is obviously over 10 years old, maybe it should be removed so as not to confuse users. Timo 2015-09-02 0:44 GMT+02:00 Wayne Fay : > SVN says Brett posted that file (over 10 yrs ago), so maybe he can tell us > more: > > "Added Mon Apr 18 07:07:58 2005 UTC (10 years, 4 months ago) by brett" > http://svn.apache.org/viewvc/maven/plugins/tags/maven-assembly-plugin-2.5.5/src/main/resources/assemblies/jar-with-dependencies.xml?view=log > > I scanned quickly and found some files in the JarJar project you > linked to that date back to Aug 2004, so I suspect that is what he is > talking about, but can't really be certain... > > Wayne > > On Tue, Sep 1, 2015 at 1:25 PM, Timo wrote: >> Hello everyone, >> >> a question on Stack Overflow made me curious about the following line >> in the jar-with-dependencies example descriptor file >> (http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies): >> >> >> >> What does this mean? Is it refering to jarjar >> (https://code.google.com/p/jarjar/) or to something like what the >> Spring Boot Maven plugin does? >> >> Thanks for any insight! >> Timo >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release with sub modules have miss match version??
Thanks Stephen, it is very helpful -Dan On Wed, Sep 2, 2015 at 12:50 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I have done it (by accident). It works but is super annoying... Especially > when you end up with and off-by-one version number in a couple of the > modules... > > (Happened when some developer wanted to do a point release of one module > and kicked off the über-release so that one went to 1.5.1 and everything > else to 1.6... Then the subsequent "fixing" of their mistake... Which was > only discovered with everything else on 1.11 while that module was on 1.5.6 > and we'd gained a 1.8.3 and a 1.10.1 module thanks to copycat developers... > Well that was "fun") > > Don't do it is my recommendation. If they need different version numbers > then they most likely need separate release lifecycles and thus should be > separate release roots > > On Tuesday, September 1, 2015, Dan Tran wrote: > > > Thanks Robert, > > > > if anyone has done this scenario, please share your experience :-) > > > > -Dan > > > > On Tue, Sep 1, 2015 at 8:51 AM, Robert Scholte > > wrote: > > > > > it should support separate versions, although it is not the best > > practice. > > > try running it with -DdryRun first to confirm. > > > > > > Robert > > > > > > Op Tue, 01 Sep 2015 17:04:16 +0200 schreef Dan Tran > >: > > > > > > > > > Hi, > > >> > > >> is it possible that release plugin can handle this situation? > > >> > > >> Or the entire release tree must use the same release version. Period > > >> > > >> Thanks > > >> > > >> -Dan > > >> > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > -- > Sent from my phone >
