99% of the code you need is in a shared component that you can reuse write a maven plugin to do this for you if you really see a need.
IMHO there is no need as people should just release correctly or else just deploy the ant built artifacts without maven On 10/03/2009, Lachlan Deck <lachlan.d...@gmail.com> wrote: > On 11/03/2009, at 9:12 AM, Stephen Connolly wrote: > >> edit the version in thepom andjust run mvn deploy > > More work? Sure I can create an ant-file that will recursively follow > the modules down editing all of them to do this - but that's what the > release plugin does already right? A bit of re-use wouldn't go astray > here... > > >> On 10/03/2009, Lachlan Deck <lachlan.d...@gmail.com> wrote: >>> On 10/03/2009, at 9:06 PM, Stephen Connolly wrote: >>> >>>> ehhh what's wrong with "mvn deploy"... that will deploy the current >>>> version >>>> (which should be a -SNAPSHOT)... >>> >>> Because, quite simply, I don't want to link my projects against a >>> snapshot. The svn version is repeatable. >>> >>>> in all other cases you should be using a >>>> qualifier that identifies you as the builder... >>>> >>>> for example if I want to deploy my own version of something that is >>>> currently 5.0.0-SNAPSHOT I would deploy it as version 5.0.0-onedash- >>>> r1234 >>> >>> How are you doing this? >>> >>>> where r1234 is the subversion revision... and by way of explanation >>>> I own >>>> the one-dash.com domain. >>>> >>>> if you don't use a qualifier you will mess up the maven version >>>> determinism >>>> or risk a conflict with the real project when they do decide to roll >>>> the >>>> 1234rd patch of 5ยท0.0 >>> >>> I can assure you that the projects I have in mind have no intention >>> of >>> releasing maven builds. The main build system is using ant, it's not >>> deployed to a repo, and the pom files in the projects are there to >>> please the maven people - but they remain snapshots. >>> >>>> If you are doing this for non-personal use... >>> >>> This is both for my company's intranet repo but also for a community >>> of people using the same projects. Simplicity is key. >>> >>>> I would recommend mirroring >>>> their svn repo using either git-svn or svnsync or tailor and >>>> maintaining >>>> your own branch and releasing from that branch... >>> >>> While I appreciate that this might be ideal - that's just more work >>> compared with doing what I suggested which is simple. >>> >>>> you'd also want to change >>>> the groupId's to belong to your company's domain. >>> >>> Perhaps, again if I wanted more work. The suggested additional >>> goal's >>> description could very well suggest all these things as 'better >>> alternatives' but allow people to run the goal anyway for >>> convenience's sake. It wouldn't be the first maven plugin to do so... >>> >>>> -Stephen >>>> >>>> 2009/3/10 Lachlan Deck <lachlan.d...@gmail.com> >>>> >>>>> Hi there, >>>>> >>>>> I'd like to see either an additional goal (e.g., release:deploy) >>>>> added to >>>>> the release plugin or perhaps it can be achieved via properties. >>>>> >>>>> Essentially, as far as I understand it, the release plugin requires >>>>> access >>>>> to an scm repository to commit changes to in addition to deploying >>>>> the >>>>> artifacts to the relevant maven repo. >>>>> >>>>> There's often projects out there, however, that just don't release >>>>> their >>>>> stuff or only provide snapshot builds (e.g., as their primary build >>>>> system >>>>> is ant-based).. yet anonymous cvs/svn access is free for all. >>>>> >>>>> So, in order to help facilitate deploying psuedo-released versions >>>>> of such >>>>> third-party projects to an intranet for example, it'd be a great >>>>> addition to >>>>> the release plugin in my view if it were possible to take a >>>>> snapshot and >>>>> deploy a release to some repo without the need for scm commits. >>>>> >>>>> e.g., the goal would be to deploy a 5.0.0-SNAPSHOT, for example, as >>>>> 5.0.0.1234 where 1234 is the svn version. >>>>> >>>>> I've checked out the source for the release plugin to have a poke >>>>> around >>>>> and it appears that the above would be relatively trivial to do. >>>>> Just >>>>> wondering if: >>>>> a) is this already possible? Did I miss something? >>>>> b) if not already possible, would one of the main contributors to >>>>> the >>>>> plugin like to add this -- given you're familiar already with how >>>>> best to >>>>> achieve this with the project >>>>> c) otherwise, any objections to this or other suggestions? >>>>> >>>>> Thanks. >>>>> >>>>> with regards, >>>>> -- >>>>> >>>>> Lachlan Deck >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>>>> For additional commands, e-mail: users-h...@maven.apache.org >>>>> >>>>> >>> >>> with regards, >>> -- >>> >>> Lachlan Deck >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> 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 >> > > with regards, > -- > > Lachlan Deck > > > > > --------------------------------------------------------------------- > 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
