Re: Best Practices for Managing Maven with Branches

[Ed Hillmann]

I've had very good experience with the goals on the release plugin.  It
pretty much does what is required for my branching needs.

Thanks,
Ed


On Tue, Jan 15, 2013 at 3:38 AM, Nick Stolwijk wrote:

> Or take a look at the Maven Release Plugin - branch goal [1] and it's
> documentation page [2].
>
> [1]
> http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html
> [2]
>
> http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html
>
> Hth,
>
> Nick Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>
>
> On Mon, Jan 14, 2013 at 6:23 PM, Manfred Moser 
> wrote:
>
> > The mvn versions plugin can do the update of the pom... but the branching
> > and stuff can be done with the scm plugin.
> >
> > If you want it completely automated you have to roll those together on
> > your own somehow.
> >
> > On Mon, January 14, 2013 9:06 am, John Kramer wrote:
> > > Are there any automated tools for that or should I write my own
> > > see/perl/something?
> > >
> > > John Kramer
> > > email: jkra...@mojiva.com
> > > mobile: 314.435.2370
> > > skype: kramer.mojiva
> > > twitter: @KramerKnowsTech 
> > > 0xCAFEBABE0032
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On 1/14/13 11:43 AM, "Manfred Moser"  wrote:
> > >
> > >>A very common and well working approach is to have a branch qualifier
> in
> > >>the version and change the version of your project with the versions
> > >>plugin.
> > >>
> > >>So e.g. you would have
> > >>
> > >>1.1.2-brancha-SNASPHOT
> > >>1.1.2-branchb-SNASPHOT
> > >>
> > >>and to update them after you cut the branch in your scm you could use
> > >>
> > >>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT
> > >>
> > >>manfred
> > >>
> > >>
> > >>On Mon, January 14, 2013 8:39 am, John Kramer wrote:
> > >>> Hi guys,
> > >>>
> > >>> Please forgive me if this seems like a newbie question.
> > >>>
> > >>>
> > >>> I am reasonably seasoned with Maven, but have never really handle
> > >>> branching myself, and now I am put in the position where I am going
> to
> > >>> have to.  I.e.  What I am asking here is when I branch in git (or svn
> > >>> or
> > >>> whatever) how do I manage versions in poms (and any other versions I
> am
> > >>> not thinking about)?
> > >>>
> > >>>
> > >>> Could someone point me at best practices for branches?
> > >>>
> > >>> Thanks!
> > >>>
> > >>>
> > >>> John Kramer
> > >>> email: jkra...@mojiva.com
> > >>> mobile: 314.435.2370
> > >>> skype: kramer.mojiva
> > >>> twitter: @KramerKnowsTech
> > >>> 0xCAFEBABE0032
> > >>>
> > >>>
> > >>
> > >>
> > >>-
> > >>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: Escape '*' in property command line

[Billy Newman]

I did try single quotes, unfortunately that did not work either.

I modified the maven script to print out is quoted args variable,
looks like it did some sort of filename expansion with the '*'
character.

When I perform:
echo "0 0 23 * * *" I get:
0 0 23 * * *, as one would expect.

Seems like a bug in the maven script that is creating the QUOTED_ARGS
variable at the beginning of the script.

Billy

On Mon, Jan 14, 2013 at 2:01 PM, Curtis Rueden  wrote:
> Hi Billy,
>
>> I actually get a directory listing of the current directory in which
>> the pom is executing.
>
> That sounds more like your shell is interpreting the asterisks as globs.
>
> Did you try it with single quotes instead of double quotes?
>
> -Curtis
>
>
> On Mon, Jan 14, 2013 at 2:57 PM, Billy Newman  wrote:
>
>> Using maven 2.
>>
>> I am trying to pass a cron expression as a property in a maven build.
>>
>> mvn clean install -Dcron-expression="0 0 23 * * *"
>>
>> However it looks like the maven script is doing something funky with
>> the '*' characters before actually passing them off to java.  I
>> actually get a directory listing of the current directory in which the
>> pom is executing.
>>
>> I have tried escaping to no avail.
>>
>> Anyone run into this before?
>>
>> Thanks.
>>
>> -
>> 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: Escape '*' in property command line

[Curtis Rueden]

Hi Billy,

> I actually get a directory listing of the current directory in which
> the pom is executing.

That sounds more like your shell is interpreting the asterisks as globs.

Did you try it with single quotes instead of double quotes?

-Curtis


On Mon, Jan 14, 2013 at 2:57 PM, Billy Newman  wrote:

> Using maven 2.
>
> I am trying to pass a cron expression as a property in a maven build.
>
> mvn clean install -Dcron-expression="0 0 23 * * *"
>
> However it looks like the maven script is doing something funky with
> the '*' characters before actually passing them off to java.  I
> actually get a directory listing of the current directory in which the
> pom is executing.
>
> I have tried escaping to no avail.
>
> Anyone run into this before?
>
> Thanks.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Escape '*' in property command line

[Billy Newman]

Using maven 2.

I am trying to pass a cron expression as a property in a maven build.

mvn clean install -Dcron-expression="0 0 23 * * *"

However it looks like the maven script is doing something funky with
the '*' characters before actually passing them off to java.  I
actually get a directory listing of the current directory in which the
pom is executing.

I have tried escaping to no avail.

Anyone run into this before?

Thanks.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Site plugin to document properties in the pom?

[Graham Leggett]

On 14 Jan 2013, at 10:02 PM, Mirko Friedenhagen  wrote:

> I once was successful with referencing injected properties in velocity
> by using the get method. Maybe something like:
> ${project.properties.get("tomcat.port.http.confluence43.live")}
> will work?

Alas, no.

The idea is that the properties in the pom and the properties published to the 
site are always in sync, even after the current crop of architects have moved 
on from the project. If you have to add a property in two steps, there is no 
way the project will stay in sync.

Regards,
Graham
--



smime.p7s
Description: S/MIME cryptographic signature

Re: Site plugin to document properties in the pom?

[Mirko Friedenhagen]

Hello Graham,

I once was successful with referencing injected properties in velocity
by using the get method. Maybe something like:
${project.properties.get("tomcat.port.http.confluence43.live")}
will work?

Regards Mirko

On Mon, Jan 14, 2013 at 5:40 PM, Graham Leggett  wrote:
> On 14 Jan 2013, at 6:36 PM, Olivier Lamy  wrote:
>
>> maybe 
>> http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering
>
> Doesn't seem to fit, alas, as you have to come up with your own template and 
> manually add the new properties to the template.
>
> In addition, my properties contain dots:
>
>   
> 
> 7999
> 
> 7998
> 7997
> 127.0.0.1
>   
>
> Regards,
> Graham
> --
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Some questions about Webby

[Martin Gainty]

Another great tool to have in your toolbelt

IMHO: most IDEs (not only eclipse) will allow debugging HTTP 1.0/HTTP 1.1 
Connections

i havent seen any tool except openssl and curl for debugging SSL connections 
..picture the following 2 scenarios

Client has wrong key for cert or vice-versa..happens alot with self-signed 
certs..how to debug this except for logging?
Server has wrong cipher for client public-key algo...so when handshake fails 
and key-exchange doesnt happen..how to debug?
Saludos desde EEUU!
Martin 
__ 
Porfavor..no altere o interrumpir esta communicacion..Gracias
 > Date: Mon, 14 Jan 2013 18:54:09 +
> Subject: Re: Some questions about Webby
> From: migueldealme...@gmail.com
> To: users@maven.apache.org; thorsten.h...@vkb.de
> 
> Hey Thorsten,
> 
> Did you manage to figure out this? I've just asked the exact same thing in
> m2e's mailing list!
> 
> Cheers,
> 
> Miguel Almeida
> 
> 
> On Tue, May 8, 2012 at 2:47 PM, Thorsten Heit  wrote:
> 
> > Hi,
> >
> > today I decided to give Webby a try. Apart from Webby Core I also
> > installed the embedded Jetty 8.x container. So far, so good.
> >
> > Some questions:
> >
> > a) How does Webby deal with dependencies having their scope set to
> > "provided"?
> >
> > Our applications are mostly WARs / EARs that are deployed into WebSphere
> > Application Server 7.x. Therefore a couple of dependencies such as
> > javax.servlet:servlet-api or javax.mail:mail are specified in the
> > pom.xml's with scope "provided".
> >
> > Using such an application with the embedded Jetty container results in
> > ClassNotFoundExceptions; using a local Tomcat 7.x installation (on which I
> > have the necessary jars copied into the lib folder) works, although it
> > seems to me to take a bit longer for startup.
> >
> >
> > b) Can I use Webby to debug web applications via HTTPS?
> >
> > The locally installed Tomcat instance is already configured for accepting
> > SSL connections. This works well as long as I'm debugging my application
> > via Eclipse, WTP and m2eclipse-wtp, but obviously not when using Webby.
> > Creating a run or debug configuration lets me only choose a normal HTTP
> > port, but there's nothing about HTTPS...
> >
> >
> > Regards
> >
> > Thorsten
  

Re: Best Practices for Managing Maven with Branches

[Manfred Moser]

True... provided your scm system supports all that ;-)

In most cases it should work.

On Mon, January 14, 2013 9:38 am, Nick Stolwijk wrote:
> Or take a look at the Maven Release Plugin - branch goal [1] and it's
> documentation page [2].
>
> [1]
> http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html
> [2]
> http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html
>
> Hth,
>
> Nick Stolwijk
>
> ~~~ Try to leave this world a little better than you found it and, when
> your turn comes to die, you can die happy in feeling that at any rate you
> have not wasted your time but have done your best ~~~
>
> Lord Baden-Powell
>
>
> On Mon, Jan 14, 2013 at 6:23 PM, Manfred Moser 
> wrote:
>
>> The mvn versions plugin can do the update of the pom... but the
>> branching
>> and stuff can be done with the scm plugin.
>>
>> If you want it completely automated you have to roll those together on
>> your own somehow.
>>
>> On Mon, January 14, 2013 9:06 am, John Kramer wrote:
>> > Are there any automated tools for that or should I write my own
>> > see/perl/something?
>> >
>> > John Kramer
>> > email: jkra...@mojiva.com
>> > mobile: 314.435.2370
>> > skype: kramer.mojiva
>> > twitter: @KramerKnowsTech 
>> > 0xCAFEBABE0032
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On 1/14/13 11:43 AM, "Manfred Moser"  wrote:
>> >
>> >>A very common and well working approach is to have a branch qualifier
>> in
>> >>the version and change the version of your project with the versions
>> >>plugin.
>> >>
>> >>So e.g. you would have
>> >>
>> >>1.1.2-brancha-SNASPHOT
>> >>1.1.2-branchb-SNASPHOT
>> >>
>> >>and to update them after you cut the branch in your scm you could use
>> >>
>> >>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT
>> >>
>> >>manfred
>> >>
>> >>
>> >>On Mon, January 14, 2013 8:39 am, John Kramer wrote:
>> >>> Hi guys,
>> >>>
>> >>> Please forgive me if this seems like a newbie question.
>> >>>
>> >>>
>> >>> I am reasonably seasoned with Maven, but have never really handle
>> >>> branching myself, and now I am put in the position where I am going
>> to
>> >>> have to.  I.e.  What I am asking here is when I branch in git (or
>> svn
>> >>> or
>> >>> whatever) how do I manage versions in poms (and any other versions I
>> am
>> >>> not thinking about)?
>> >>>
>> >>>
>> >>> Could someone point me at best practices for branches?
>> >>>
>> >>> Thanks!
>> >>>
>> >>>
>> >>> John Kramer
>> >>> email: jkra...@mojiva.com
>> >>> mobile: 314.435.2370
>> >>> skype: kramer.mojiva
>> >>> twitter: @KramerKnowsTech
>> >>> 0xCAFEBABE0032
>> >>>
>> >>>
>> >>
>> >>
>> >>-
>> >>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
>>
>>
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Some questions about Webby

[Miguel Almeida]

Hey Thorsten,

Did you manage to figure out this? I've just asked the exact same thing in
m2e's mailing list!

Cheers,

Miguel Almeida


On Tue, May 8, 2012 at 2:47 PM, Thorsten Heit  wrote:

> Hi,
>
> today I decided to give Webby a try. Apart from Webby Core I also
> installed the embedded Jetty 8.x container. So far, so good.
>
> Some questions:
>
> a) How does Webby deal with dependencies having their scope set to
> "provided"?
>
> Our applications are mostly WARs / EARs that are deployed into WebSphere
> Application Server 7.x. Therefore a couple of dependencies such as
> javax.servlet:servlet-api or javax.mail:mail are specified in the
> pom.xml's with scope "provided".
>
> Using such an application with the embedded Jetty container results in
> ClassNotFoundExceptions; using a local Tomcat 7.x installation (on which I
> have the necessary jars copied into the lib folder) works, although it
> seems to me to take a bit longer for startup.
>
>
> b) Can I use Webby to debug web applications via HTTPS?
>
> The locally installed Tomcat instance is already configured for accepting
> SSL connections. This works well as long as I'm debugging my application
> via Eclipse, WTP and m2eclipse-wtp, but obviously not when using Webby.
> Creating a run or debug configuration lets me only choose a normal HTTP
> port, but there's nothing about HTTPS...
>
>
> Regards
>
> Thorsten

Re: Best Practices for Managing Maven with Branches

[Nick Stolwijk]

Or take a look at the Maven Release Plugin - branch goal [1] and it's
documentation page [2].

[1]
http://maven.apache.org/maven-release/maven-release-plugin/branch-mojo.html
[2]
http://maven.apache.org/maven-release/maven-release-plugin/examples/branch.html

Hth,

Nick Stolwijk

~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~

Lord Baden-Powell


On Mon, Jan 14, 2013 at 6:23 PM, Manfred Moser  wrote:

> The mvn versions plugin can do the update of the pom... but the branching
> and stuff can be done with the scm plugin.
>
> If you want it completely automated you have to roll those together on
> your own somehow.
>
> On Mon, January 14, 2013 9:06 am, John Kramer wrote:
> > Are there any automated tools for that or should I write my own
> > see/perl/something?
> >
> > John Kramer
> > email: jkra...@mojiva.com
> > mobile: 314.435.2370
> > skype: kramer.mojiva
> > twitter: @KramerKnowsTech 
> > 0xCAFEBABE0032
> >
> >
> >
> >
> >
> >
> >
> > On 1/14/13 11:43 AM, "Manfred Moser"  wrote:
> >
> >>A very common and well working approach is to have a branch qualifier in
> >>the version and change the version of your project with the versions
> >>plugin.
> >>
> >>So e.g. you would have
> >>
> >>1.1.2-brancha-SNASPHOT
> >>1.1.2-branchb-SNASPHOT
> >>
> >>and to update them after you cut the branch in your scm you could use
> >>
> >>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT
> >>
> >>manfred
> >>
> >>
> >>On Mon, January 14, 2013 8:39 am, John Kramer wrote:
> >>> Hi guys,
> >>>
> >>> Please forgive me if this seems like a newbie question.
> >>>
> >>>
> >>> I am reasonably seasoned with Maven, but have never really handle
> >>> branching myself, and now I am put in the position where I am going to
> >>> have to.  I.e.  What I am asking here is when I branch in git (or svn
> >>> or
> >>> whatever) how do I manage versions in poms (and any other versions I am
> >>> not thinking about)?
> >>>
> >>>
> >>> Could someone point me at best practices for branches?
> >>>
> >>> Thanks!
> >>>
> >>>
> >>> John Kramer
> >>> email: jkra...@mojiva.com
> >>> mobile: 314.435.2370
> >>> skype: kramer.mojiva
> >>> twitter: @KramerKnowsTech
> >>> 0xCAFEBABE0032
> >>>
> >>>
> >>
> >>
> >>-
> >>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
>
>

assembly plugin, permissions, and **/*

[Steve Cohen]

I have noticed the following behavior that seems strange to me.

I am using the assembly plugin to create a tar.gz archive.  I have 
several filesets that I use, and they all specify file and directory 
permissions.  Some filesets create a single target directory from a 
single source directory and move in all the files in that directory. 
There is no directory recursion involved and it works fine, using 
**.  The archive contains an entry for that 
directory, with the proper permissions.


One directory has a subdirectory and I also want to make a fileset out 
of that.  In that directory I was using **/*.  All 
the files that needed to be included were included with the right 
permissions and there was an entry in the archive for the subdirectory 
with the right permissions.


However, there was no entry for the top directory of this fileset and so 
when the archive was extracted, the directory created had the default 
rather than the desired permissions.


I fixed this (bandaided it) with
**
**/*

Should this be necessary?  What am I missing? Why isn't a directory 
created for the root of the fileset in the archive when only 
**/* is specified?



-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Best Practices for Managing Maven with Branches

[Manfred Moser]

The mvn versions plugin can do the update of the pom... but the branching
and stuff can be done with the scm plugin.

If you want it completely automated you have to roll those together on
your own somehow.

On Mon, January 14, 2013 9:06 am, John Kramer wrote:
> Are there any automated tools for that or should I write my own
> see/perl/something?
>
> John Kramer
> email: jkra...@mojiva.com
> mobile: 314.435.2370
> skype: kramer.mojiva
> twitter: @KramerKnowsTech 
> 0xCAFEBABE0032
>
>
>
>
>
>
>
> On 1/14/13 11:43 AM, "Manfred Moser"  wrote:
>
>>A very common and well working approach is to have a branch qualifier in
>>the version and change the version of your project with the versions
>>plugin.
>>
>>So e.g. you would have
>>
>>1.1.2-brancha-SNASPHOT
>>1.1.2-branchb-SNASPHOT
>>
>>and to update them after you cut the branch in your scm you could use
>>
>>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT
>>
>>manfred
>>
>>
>>On Mon, January 14, 2013 8:39 am, John Kramer wrote:
>>> Hi guys,
>>>
>>> Please forgive me if this seems like a newbie question.
>>>
>>>
>>> I am reasonably seasoned with Maven, but have never really handle
>>> branching myself, and now I am put in the position where I am going to
>>> have to.  I.e.  What I am asking here is when I branch in git (or svn
>>> or
>>> whatever) how do I manage versions in poms (and any other versions I am
>>> not thinking about)?
>>>
>>>
>>> Could someone point me at best practices for branches?
>>>
>>> Thanks!
>>>
>>>
>>> John Kramer
>>> email: jkra...@mojiva.com
>>> mobile: 314.435.2370
>>> skype: kramer.mojiva
>>> twitter: @KramerKnowsTech
>>> 0xCAFEBABE0032
>>>
>>>
>>
>>
>>-
>>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: Best Practices for Managing Maven with Branches

[John Kramer]

Are there any automated tools for that or should I write my own
see/perl/something?

John Kramer
email: jkra...@mojiva.com
mobile: 314.435.2370
skype: kramer.mojiva
twitter: @KramerKnowsTech 
0xCAFEBABE0032







On 1/14/13 11:43 AM, "Manfred Moser"  wrote:

>A very common and well working approach is to have a branch qualifier in
>the version and change the version of your project with the versions
>plugin.
>
>So e.g. you would have
>
>1.1.2-brancha-SNASPHOT
>1.1.2-branchb-SNASPHOT
>
>and to update them after you cut the branch in your scm you could use
>
>mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT
>
>manfred
>
>
>On Mon, January 14, 2013 8:39 am, John Kramer wrote:
>> Hi guys,
>>
>> Please forgive me if this seems like a newbie question.
>>
>>
>> I am reasonably seasoned with Maven, but have never really handle
>> branching myself, and now I am put in the position where I am going to
>> have to.  I.e.  What I am asking here is when I branch in git (or svn or
>> whatever) how do I manage versions in poms (and any other versions I am
>> not thinking about)?
>>
>>
>> Could someone point me at best practices for branches?
>>
>> Thanks!
>>
>>
>> John Kramer
>> email: jkra...@mojiva.com
>> mobile: 314.435.2370
>> skype: kramer.mojiva
>> twitter: @KramerKnowsTech
>> 0xCAFEBABE0032
>>
>>
>
>
>-
>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: Best Practices for Managing Maven with Branches

[Manfred Moser]

A very common and well working approach is to have a branch qualifier in
the version and change the version of your project with the versions
plugin.

So e.g. you would have

1.1.2-brancha-SNASPHOT
1.1.2-branchb-SNASPHOT

and to update them after you cut the branch in your scm you could use

mvn versions:set -=DnewVersion= 1.1.2-brancha-SNAPSHOT

manfred


On Mon, January 14, 2013 8:39 am, John Kramer wrote:
> Hi guys,
>
> Please forgive me if this seems like a newbie question.
>
>
> I am reasonably seasoned with Maven, but have never really handle
> branching myself, and now I am put in the position where I am going to
> have to.  I.e.  What I am asking here is when I branch in git (or svn or
> whatever) how do I manage versions in poms (and any other versions I am
> not thinking about)?
>
>
> Could someone point me at best practices for branches?
>
> Thanks!
>
>
> John Kramer
> email: jkra...@mojiva.com
> mobile: 314.435.2370
> skype: kramer.mojiva
> twitter: @KramerKnowsTech
> 0xCAFEBABE0032
>
>


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Site plugin to document properties in the pom?

[Graham Leggett]

On 14 Jan 2013, at 6:36 PM, Olivier Lamy  wrote:

> maybe 
> http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering

Doesn't seem to fit, alas, as you have to come up with your own template and 
manually add the new properties to the template.

In addition, my properties contain dots:

  

7999

7998
7997
127.0.0.1
  

Regards,
Graham
--



smime.p7s
Description: S/MIME cryptographic signature

Best Practices for Managing Maven with Branches

[John Kramer]

Hi guys,

Please forgive me if this seems like a newbie question.


I am reasonably seasoned with Maven, but have never really handle branching 
myself, and now I am put in the position where I am going to have to.  I.e.  
What I am asking here is when I branch in git (or svn or whatever) how do I 
manage versions in poms (and any other versions I am not thinking about)?


Could someone point me at best practices for branches?

Thanks!


John Kramer
email: jkra...@mojiva.com
mobile: 314.435.2370
skype: kramer.mojiva
twitter: @KramerKnowsTech
0xCAFEBABE0032

Re: Site plugin to document properties in the pom?

[Olivier Lamy]

maybe 
http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering


2013/1/14 Graham Leggett :
> Hi all,
>
> I am looking for a plugin that will take the properties defined in the POM, 
> and include these properties in the generated site.
>
> Does such a plugin exist?
>
> The problem I am trying to solve is that I have properties defined in a 
> parent POM, and would like to expose these properties in documentation 
> without manually copying the properties into a wiki or have some other manual 
> process.
>
> Regards,
> Graham
> --
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Site plugin to document properties in the pom?

[Graham Leggett]

Hi all,

I am looking for a plugin that will take the properties defined in the POM, and 
include these properties in the generated site.

Does such a plugin exist?

The problem I am trying to solve is that I have properties defined in a parent 
POM, and would like to expose these properties in documentation without 
manually copying the properties into a wiki or have some other manual process.

Regards,
Graham
--



smime.p7s
Description: S/MIME cryptographic signature