Re: Git settings for maven release plugin...
http://www.sonatype.com/people/2009/09/maven-tips-and-tricks-using-github/ using scm:git:git should do the trick. /Anders On Fri, 2013-03-22 at 00:10 +0100, Jeff wrote: > > > scm:git:ssh://g...@github.com:MyOrg/apps-thor.git > > scm:git:ssh://g...@github.com:MyOrg/apps-thor.git > g...@github.com:MyOrg/apps-thor.git > > Am I missing something obvious? > > > Regards! > >
Re: Maven (3.0.4) dependency plugin difference in ordering between build-classpath and tree
Thanks Anders, I had forgotten to retest my issue when the new releases came. My ticket is now closed. /Anders On Thu, 2013-01-17 at 09:47 +0100, Anders Hammar wrote: > I just tested the test project attached to the jira ticket and can't > reproduce. Please follow up in that ticket! > > /Anders > > > On Thu, Jan 17, 2013 at 9:09 AM, Anders Lindgren < > anders.lindg...@cinnober.com> wrote: > > > Hi, > > > > I reported this almost a year ago > > http://jira.codehaus.org/browse/MDEP-342 > > > > I don't know what's is going wrong or why, please comment on the jira if > > you have more info to provide. > > > > /Anders > > > > > > On Wed, 2013-01-16 at 10:03 +0100, Pram wrote: > > > > > Hi, > > > > > > I posted a question on Stackoverflow yesterday ( > > http://stackoverflow.com/questions/14336801/maven-dependency-plugin-difference-in-ordering-between-build-classpath-and-tree) > > and it was recommended that I ask it again on the user mailing list. > > > > > > Essentially I'm seeing a difference in the ordering of the output of > > tree and build-classpath. > > > > > > Output from tree http://pastebin.com/J2Q6iTK6 > > > Output from build-classpath http://pastebin.com/k2SdrHP7 > > > > > > Can anyone provide any insight into why this may be happening? > > > > > > thanks > > > > > > Pram > > > > > > > > >
Re: Maven (3.0.4) dependency plugin difference in ordering between build-classpath and tree
Hi, I reported this almost a year ago http://jira.codehaus.org/browse/MDEP-342 I don't know what's is going wrong or why, please comment on the jira if you have more info to provide. /Anders On Wed, 2013-01-16 at 10:03 +0100, Pram wrote: > Hi, > > I posted a question on Stackoverflow yesterday > (http://stackoverflow.com/questions/14336801/maven-dependency-plugin-difference-in-ordering-between-build-classpath-and-tree) > and it was recommended that I ask it again on the user mailing list. > > Essentially I'm seeing a difference in the ordering of the output of tree and > build-classpath. > > Output from tree http://pastebin.com/J2Q6iTK6 > Output from build-classpath http://pastebin.com/k2SdrHP7 > > Can anyone provide any insight into why this may be happening? > > thanks > > Pram >
Re: Properties within source code
Hi Nick,
I think you missed the filtering part. I are supposed to enable the
filtering by true
See
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
As you can see there, it also possible to put you variables in a
separate properties file.
Hopes it helps
/Anders
On Fri, 2012-11-16 at 22:53 +0100, Nick Cuneo (ncuneo) wrote:
> Hi,
>
>
>
> We are attempting to migrate our build environment from being very
> Ant-centric, to be Maven-centric. We have a source file (Trace.java)
> that has a couple of variables that get set for debug/non-debug
> builds. The code is as follows
>
> public boolean DEBUG = ${debug.enabled};
>
>
>
> Obviously this won’t compile as is, but with Ant we were able to
> replace that property at compile time so it would build the
> appropriate package. I’m trying to get that same functionality with
> Maven… I’ve looked into trying to add the file as a resource and
> creating the property in the pom.xml. I’ve also tried using the
> google-replace plugin, but that didn’t seem to work well either. Am I
> just not doing it right? I’m learning Maven as I go so I figured
> that’s a possibility. I’ve tried doing searches on the subject with
> google and looking through maven documentation and it feels
> straightforward but just not working for me.
>
>
>
> Example from pom:
>
>
>
> true
>
>
>
>
>
> …
>
>
>
>
>
>
> ${basedir}/src/trace
>
>
>
>
> Trace.java
>
>
>
>
>
>
>
>
>
> I see in the log that it’s doing something with the file, maybe not
> what I was intending though:
>
> [INFO] Copying 1 resource
>
>
>
> Any help would be appreciative.
>
>
>
>
>
> Thanks,
>
> Nick
>
> Description:
> http://www.cisco.com/web/europe/images/email/signature/logo02.jpg
>
>
> Nicholas Cuneo
> Software Engineer
> SPVTG
> ncu...@cisco.com
> Phone: 1-714-434-2344
> Mobile: 1-949-243-4952
>
>
>
>
>
> 3500 Hyland Ave
> Costa Mesa, CA
> United States
> Cisco.com
>
> Download
> vCardDescription:
> Virtual Card File
>
>
>
>
>
>
> Description: Think before you print.Think before you print.
>
> This email may contain confidential and privileged material for the
> sole use of the intended recipient. Any review, use, distribution or
> disclosure by others is strictly prohibited. If you are not the
> intended recipient (or authorized to receive for the recipient),
> please contact the sender by reply email and delete all copies of this
> message.
>
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
>
>
>
>
>
>
>
>
>
>
Re: What does the "tag" parameter for release:branch do?
Hi Laird, I would guess that it is used by SCM's like CVS which takes an existing tag as base for a new branch. The explanation could be better as many of the other parameters describes SVN specific usage. /Anders On Thu, 2012-09-27 at 19:16 +0200, Laird Nelson wrote: > On Thu, Sep 27, 2012 at 9:48 AM, Laird Nelson wrote: > > > I can't figure out what the tag parameter is supposed to do for the > > maven-release-plugin branch goal. > > > > I'm guessing that this is just a mistake; much of the branch goal seems to > bear a striking similarity to the perform goal; I smell cut-and-paste. :-) > Maybe this is a property that got copied over but isn't used? > > Best, > Laird >
