or even start with http://maven.apache.org/users/index.html
and http://maven.apache.org/articles.html
regards,
Hervé
Le vendredi 13 février 2009, Hervé BOUTEMY a écrit :
> please read http://maven.apache.org/users/getting-help.html
>
> Le vendredi 13 février 2009, SRINIVASA RAO a écrit :
> > Hi
please read http://maven.apache.org/users/getting-help.html
Le vendredi 13 février 2009, SRINIVASA RAO a écrit :
> Hi All,
>
> I am new to Maven and have been asked to set up new development environment
> in my office.Till now we are using CVS on one of the remote servers and web
> server(TOMCAT 5
Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
You can regexp the comment to make sure every comment has an issue in
it, and you can tweak the dialog so it has a prompt for the issue.
Otherwise it doesn't do much else that I recall...it's just an
aid/reminder to get the issue in the comment.
-Original Message-
From: Benjamin Bentmann [
Dennis Lundberg wrote:
I would like to start using bugtraq [1] in our subversion repositories.
If we set a bunch of svn properties in the repository, then version
control tools can link to issues in JIRA.
+1.
Will it automatically parse [MNG-] or does a committer need to take
special ste
Dennis Lundberg wrote:
If it's possible I'd like to continue this release with the artifacts
that were already built. I've been through hell and back already trying
to get this release out the door.
This is an interesting remark. I felt exactly the same until I tried
Nexus process. Before -
It must replace the old process because we can't accurately sync to
central the same artifacts from two places. The metadata will get hosed.
Go ahead with the vote, and then I'll do the promotion via Nexus for
you.
-Original Message-
From: Dennis Lundberg [mailto:denn...@apache.org]
Sent:
Sorry, but I haven't followed the threads about the Nexus repo as much
as would have liked. Are you saying that it has completely replaced the
old file based release repo at ASF? And that the only way to release an
ASF artifact is through the Nexus instance?
If it's possible I'd like to continue t
Hi Brian
bugtrac works the other way round. It created links to JIRA from your
version control tool. This will only happen for tools that support
bugtraq, so it's not an enforcement tool. For clients that don't support
bugtraq it makes no difference. The only thing that is changed in the
svn repo
Might not the "help:effective-pom" plugin/goal be used to validate
some of these automatically? Especially if there remains a canonical
form for the pom. As long as this (or another) plugin can get
logically equivalent, you can use xquery or xpath statements to
validate that what appears
Or, if you have a windows box, use WinMerge with the 7zip add-in
It will allow easy comparison of war, jar and ear files... and you can
dive down to see if the class files are the same (even if the date
stamps are different)
-Stephen
2009/2/12 Jason van Zyl :
>
> On 12-Feb-09, at 8:49 AM, Paul B
On 12-Feb-09, at 8:49 AM, Paul Benedict wrote:
Oleg, thank you for volunteering. j/k
My only concern is that building a project successfully does not
guarantee backwards compatibility. Things like property resolution,
etc. need to either be eye balled or loaded into an application to
show it w
Oleg, thank you for volunteering. j/k
My only concern is that building a project successfully does not
guarantee backwards compatibility. Things like property resolution,
etc. need to either be eye balled or loaded into an application to
show it works or bombs.
Binaries, sure, maybe that's overki
+1
Works fine on the company builds.
S.
Brian E. Fox wrote:
>
>> It's finally time after 8 Release Candidates:
>>
>>
>> Issues fixed:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
>> =Html&projectId=10500&Create=Create
>>
>>
>> NOTE: The urls below are using a se
Benjamin Bentmann wrote:
>
> Costin Caraivan wrote:
>
>> The invocation is from the pom.xml, inside a profile. So execution bound
>> to
>> a build lifecycle.
>
> Then consider to drop an example project in JIRA so we can have closer
> look and something to reproduce the issue. From the few bi
15 matches
Mail list logo
