The following comment has been added to this issue:
Author: Ross Burnett
Created: Tue, 23 Nov 2004 7:24 PM
Body:
I'm not sure if the current behaviour is by accident or design, but I believe
that it is correct and should not be changed.
The project.properties file is for project
On Tuesday 23 November 2004 14:19, Brett Porter wrote:
> > Jason, you are absolutely correct - the requirement is *not*
> > separate repositories. I think the fundamental requirement is
> > the ability to classify artifacts and to select artifacts based
> > on classification.
>
> I agree with Jason
Message:
The following issue has been reopened.
Reopener: Torsten Curdt
Date: Tue, 23 Nov 2004 5:30 PM
Waiting for feedback how to resolve this.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-264
H
> Jason, you are absolutely correct - the requirement is *not*
> separate repositories. I think the fundamental requirement is the
> ability to classify artifacts and to select artifacts based on
> classification.
I agree with Jason that this is getting too complicated, and what I Was pushing
t
On Tuesday 23 November 2004 11:45, Brett Porter wrote:
> I'm still not sure what you need here. When you use a SNAPSHOT,
> it is not first wins, but newest - all are checked.
>
> But you talk about changing repositories per group - aren't the
> repositories paritioned enough such that the set of gr
On Tuesday 23 November 2004 13:24, Jason van Zyl wrote:
> On Tue, 2004-11-23 at 12:17, Stephen Nesbitt wrote:
> > Not sure I follow here. Most of the time developers will work
> > against the artifacts in the QA repository.
>
> I'm watching this conversation but I'll jump in here with a
> question.
On Tue, 2004-11-23 at 12:17, Stephen Nesbitt wrote:
> Not sure I follow here. Most of the time developers will work
> against the artifacts in the QA repository.
I'm watching this conversation but I'll jump in here with a question.
Why do you need a separate repository for QA artifacts? At the
The following comment has been added to this issue:
Author: Miguel Griffa
Created: Tue, 23 Nov 2004 4:08 PM
Body:
IMHO, genapp templates shuold be dependencies. This would solve lots of issues.
Getting templates from repo would be great, but also to have dependencies
automaticall
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPGENAPP-19
Here is an overview of the issue:
-
Key
The following issue has been updated:
Updater: Miguel Griffa (mailto:[EMAIL PROTECTED])
Date: Tue, 23 Nov 2004 4:02 PM
Changes:
Attachment changed to web-velocity-template.tar.gz
-
For a full histor
Hi Geeks
I was looking for a way to retrieve a Constant value from a class in
Maven and stumbled over core:getStatic tag but this is not in 1.0 nor in
1.0.1.
Is there a reason why this is not in?
And is there a way to retrieve a constant value from a class in Maven
now?
Thanx - Andy Schaefer
-
Actually I was going to have a shot at creating a patch for this, but
when I checked the CVS, I got lost with the fact that the code appears
to be generated and I havent found time yet to figure out exactly how
:-)
-Corey
On Tue, 23 Nov 2004 23:09:06 +1100, Brett Porter <[EMAIL PROTECTED]> wrote
Does this help?
http://www.apache.org/~brett/site-2/developers/building-from-source.html#Building_Maven_with_Maven
I have a development version that I continuously use and build over the
top of (until I kill it and have to start from scratch :)
- Brett
Hardy Ferentschik wrote:
Hi there,
just wond
The Maven JAR plugin nicely creates an Implementation-Version attribute in the
JAR's manifest, looking like this:
Implementation-Version: 0.5.4-SNAPSHOT
It also adds a handful of other informational attributes.
After spending a few hours writing code to get this version string and display
it i
Hi,
Stephen Nesbitt wrote:
I think this situation is best covered by publishing to different
repositories for each, and then only utilising the remote
repositories appropriate when building. IF you happen to specify
more than one remote repository, you get the newest which should
be correct.
On Tuesday 23 November 2004 04:46, Brett Porter wrote:
Hi Brett.
You suggested I dive in so I'm going to
>
> I think this situation is best covered by publishing to different
> repositories for each, and then only utilising the remote
> repositories appropriate when building. IF you happen to sp
The following issue has been updated:
Updater: M. Sean Gilligan (mailto:[EMAIL PROTECTED])
Date: Tue, 23 Nov 2004 2:38 PM
Comment:
This is the patch that I've tested in three scenarios: 1) Using default true
value of the maven.jnlp.update.manifest property, 2) Overriding with false
Hi,
(IMMO)
* signing a jar isjust an ant call, I don't know if making it a goal is
really interessting (and all the task properties will produce much jelly
code)
* anyway as jnlp plugin objective is to generate a jnlp file, I'm not
sure if the best place for a jar:sign goal would be there, perh
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJNLP-20
Here is an overview of the issue:
-
Key:
Stephen Nesbitt wrote:
should be visited.
I am not sure that this is fine grained enough. I can imagine a use
case in which a developer has dependecies on jar A & jar B both
having the same groupId with a repository tied to say QA snapshots.
For whatever reason the developer decides that he
On Tuesday 23 November 2004 07:23, Maczka Michal wrote:
> > -Original Message-
> I forgot to add that it would be possible to make a decsion which
> repository should be hit
> using the value provided in groupId tag of the dependency.
>
> so if it is foo/baa/xxx the repositry A and
> only
epugh 2004/11/23 09:14:26
Modified:ant/xdocs changes.xml
ant project.xml
ant/src/plugin-resources/templates build.jelly
ant/src/plugin-test project.xml maven.xml
Added: ant/src/plugin-test/lib activation-1.0.2.jar
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Tue, 23 Nov 2004 12:20 PM
Body:
I have tweaked it so that included jar's that are used via jar override are
resolved properly. Instead of a get, a copy is done instead. I am using this
successf
epugh 2004/11/23 09:14:16
maven-plugins/ant/src/plugin-test/lib - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 23, 2004 3:49 PM
> To: Maven Developers List
> Subject: RE: [PROPOSAL] Ading a new tag to ?
>
> How does this help if your project relies on OSS and
> proprietary artifacts? How can I configu
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 23, 2004 3:49 PM
> To: Maven Developers List
> Subject: RE: [PROPOSAL] Ading a new tag to ?
>
>
> Maczka Michal wrote on Tuesday, November 23, 2004 12:00 PM:
>
> >> -Original Message-
Maczka Michal wrote on Tuesday, November 23, 2004 12:00 PM:
>> -Original Message-
>> From: Stephen Nesbitt
[snip]
>
>> I noticed that Jörg Schaible's post kinda made the same point with
>> the suggestion of a tag in the dependency element.
>>
>> Hows does any of this fit into"in situ" a
Hi there,
just wondering how you guys are dealing with this.
I am using maven to build my java projects and have a installed version of
maven 1.0.1.
I also would like to develop/debug the maven. I can build maven using my
installed
version of maven, but how do I get a running version maven instal
Hi brett,
awesome, I like it.
I think we should add a link to jira in the menu. It isn't enought visible
in project info.
And a link to Source Repository in Maven Developers.
Emmanuel
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROT
Hi Stephen,
I think this situation is best covered by publishing to different
repositories for each, and then only utilising the remote repositories
appropriate when building. IF you happen to specify more than one remote
repository, you get the newest which should be correct.
There are two thi
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Tue, 23 Nov 2004 7:39 AM
this looks like the antlr JAR or the commons-jelly-tags-antlr JAR are corrupt -
try deleting them and running again online.
--
> -Original Message-
> From: Stephen Nesbitt [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 23, 2004 1:14 AM
> To: [EMAIL PROTECTED]
> Cc: Vincent Massol
> Subject: Re: [PROPOSAL] Ading a new tag to ?
>
>
> On Sunday 21 November 2004 02:14, Vincent Massol wrote:
> > Hi Maven devs,
> -Original Message-
> From: Corey Scott [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 23, 2004 5:11 AM
> To: Maven Developers List
> Subject: Re: [PROPOSAL] Ading a new tag to ?
>
>
> While we are on the subject of adding tags to has a scope
> tag been considered?
Yes it is st
This has been discussed several times in the past. I must say, scope is
probably the best name I've seen for it so far.
It will get resolved in some way in the near future.
- Brett
Corey Scott wrote:
While we are on the subject of adding tags to has a scope
tag been considered? This would allow
Help on documentation is always welcome, and being a non-expert is fine
because you probably see things that long-time users miss or assume.
The best way to contribute is to pick something you think is not
explained well enough, and write it down through your own experience.
Polish it up as muc
The following comment has been added to this issue:
Author: David J. M. Karlsen
Created: Tue, 23 Nov 2004 5:31 AM
Body:
I can report the same problem:
C:\Program Files\IBM\WebSphere Studio\Application
Developer\v5.1.2\runtimes\base_v5\java\bin>java -version
java version "1.3.1"
J
36 matches
Mail list logo
