Hi Romain
I am not trying to deploy to Maven Central at all.
All I want to do is build GlassFish privately for my own purposes, so
that I do not have to wait for a promoted build say, between b79 and
b80 for a bug fix. I can build GlassFish myself, see my blog entry. I
can also deploy 4.0-SNAPSHOT already to a private Artifactory
repository, which no one else in the world can see, but me.
I want to know how to set up this ``build.id'' property outside of
editing many Maven pom.xml files, so that I can see artifacts named
like `javax.javaee-api-7.0-b80-peter.jar' so something like this. How
is ``build.id'' configured?
On 19 March 2013 10:25, Romain Grecourt <romain.grecourt_at_oracle.com> wrote:
> Hi Peter,
>
> Please don't deploy modified artifacts under official GAV (it creates
> different versions of a given GAV).
>
> Can you explain us what you want to achieve ?
>
> Thanks,
> Romain
>
>
> On 3/18/13 3:56 PM, Peter Pilgrim wrote:
>>
>> Hello All
>>
>> I have been building GlassFish 4.0 privately from the current source
>> code. I wrote a blog entry about my recent experience
>> http://www.xenonique.co.uk/blog/?p=1088
>> There one last piece of the puzzle that I have yet to solve.
>>
>> How do you configure the Maven build.id property from an external file
>> and/or from the command line?
>>
>
--
Peter Pilgrim,
**Java Champion**,
Java EE Software Development / Design / Architect for `BlueChip'
enterprises, London, UK
JavaFX ++ Scala ++ Groovy ++ Android ++ Java
:: http://www.xenonique.co.uk/blog/ ::
:: http://twitter.com/peter_pilgrim ::
:: http://audio.fm/profile/peter_pilgrim ::
:: Skype Call peter_pilgrim ::
:: http://java-champions.java.net/ ::