examine impact of multiple repositories on metadata
---
Key: MNG-639
URL: http://jira.codehaus.org/browse/MNG-639
Project: Maven 2
Type: Bug
Components: maven-artifact
Reporter: Brett Porter
Fix For: 2.0-beta-
incorrectly validating 1..1 multiplicity associations in model
--
Key: MNG-638
URL: http://jira.codehaus.org/browse/MNG-638
Project: Maven 2
Type: Bug
Components: maven-model
Reporter: Brett Porter
Brett Porter wrote:
Looks ok to me, though I don't know why we shouldn't just drop the
ant:cvs part altogether and use scm:checkout as you have in the
otherwise blocks. What do you think?
I tried that but could not get cvs to work in a way that would preserve
backward compatibility. I will pla
Looks ok to me, though I don't know why we shouldn't just drop the
ant:cvs part altogether and use scm:checkout as you have in the
otherwise blocks. What do you think?
Emmanuel, do you have any thoughts? I'm not overly familiar with the plugin.
- Brett
Phil Steitz wrote:
> Last week I added a p
Last week I added a patch to MPJDIFF-6 here:
http://jira.codehaus.org/browse/MPJDIFF-6?page=all
Comments?
Phil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MAVEN-1649?page=all ]
Brett Porter updated MAVEN-1649:
Fix Version: 1.1-beta-2
> Using ant:xslt with an xmlcatalog works fine with 1.0.2 but not with 1.1-beta1
> --
Using ant:xslt with an xmlcatalog works fine with 1.0.2 but not with 1.1-beta1
--
Key: MAVEN-1649
URL: http://jira.codehaus.org/browse/MAVEN-1649
Project: maven
Type: Bug
Components: jelly/
[ http://jira.codehaus.org/browse/MNG-226?page=comments#action_43357 ]
Brett Porter commented on MNG-226:
--
We have "build extensions" - ie providers for wagon, scm that are not
really plugins but additional providers for a particular plexus role.
Currently,
[ http://jira.codehaus.org/browse/MNG-598?page=comments#action_43356 ]
Brett Porter commented on MNG-598:
--
We don't want to have to resolve and search all
the plugins to find a missing dependency type. For this, we can add
true|false to the element, eg:
I prefer 4) with the logged warnings. With 2) you potentially create more
significant runtime problems.
If, however, you decide to go with 2), a file included in an obvious
location (i.e., WEB-INF/lib/runtime.txt) listing the dropped dependencies
would help with the troubleshooting sessions.
Kri
Distribution:
http://maven.zones.apache.org/~maven/builds/m2-20050725.001502.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/m2-build-log-20050725.001502.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
Jason van Zyl wrote:
>>2) scope in end POM always wins
>>
>>
>To me this would seem to be the most obvious the user.
>
>
I agree, given the current use of dependencies.
>
>
>>4) keep it as is (where you can use to force
>>the appropriate scope)
>>
>>
>Wouldn't that be a little inconv
setup and use a temporary snapshot repository for m2
Key: MNG-637
URL: http://jira.codehaus.org/browse/MNG-637
Project: Maven 2
Type: Task
Reporter: Brett Porter
Fix For: 2.0-beta-1
--
This message is au
On Mon, 2005-07-25 at 08:18 +1000, Brett Porter wrote:
> What this is is another dependency with a more inclusive scope down the
> chain.
>
> While the behaviour is correct, it is not intuitive. Anyone have a
> preferred option?
>
> 1) Log a warning when a higher priority scope is found in the ch
[ http://jira.codehaus.org/browse/MNG-635?page=all ]
Brett Porter closed MNG-635:
Assign To: Brett Porter
Resolution: Won't Fix
no problem, thanks!
> Webapp Resources Not Available to Unit Tests
>
>
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-448?page=comments#action_43345 ]
Martijn Dashorst commented on MAVENUPLOAD-448:
--
The correct urls are:
http://wicket.sourceforge.net/downloads/wicket-1.1-b1-bundle.jar
http://wicket.sourceforge.net/
Upload wicket-1.1-b1-bundle.jar and wicket-extensions-1.1-b1-bundle.jar
---
Key: MAVENUPLOAD-448
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-448
Project: maven-upload-requests
Type: Task
Report
[ http://jira.codehaus.org/browse/MEV-46?page=comments#action_43344 ]
Brett Porter commented on MEV-46:
-
please use a "pointer POM" for this now using the section.
> Missing JDBC POM
>
>
> Key: MEV-46
> URL: http://jira.co
What this is is another dependency with a more inclusive scope down the
chain.
While the behaviour is correct, it is not intuitive. Anyone have a
preferred option?
1) Log a warning when a higher priority scope is found in the chain
2) scope in end POM always wins
3) same as 2, but only when it is
[
http://jira.codehaus.org/browse/MAVENUPLOAD-433?page=comments#action_43331 ]
Julien Dubois commented on MAVENUPLOAD-433:
---
Hello,
Here is the upload bundle for the 1.0-RC2 release of DWR :
http://julien.dubois.free.fr/dwr/dwr-1.0-rc2-bundle.jar
+1
Brett Porter wrote:
Hi,
Can I get some opinions on making the following changes to out
repository policy?
1) no more snapshots in ibiblio
I'm happy to keep syncing these into m1 for convenience so we don't need
to change the sync app too much, but I'd like repoclean not to bring
them over
Missing JDBC POM
Key: MEV-46
URL: http://jira.codehaus.org/browse/MEV-46
Project: Maven Evangelism
Type: Bug
Components: Missing POM
Reporter: Trygve Laugstol
There is a "jdbc-stdext" pom (which is JDBC 2 IIRC) but there is still a
artifact i
On Sun, Jul 24, 2005 at 12:07:24PM +1000, Brett Porter wrote:
> Hi,
>
> Can I get some opinions on making the following changes to out
> repository policy?
1) +1
2) +1
--
Trygve
>
> 1) no more snapshots in ibiblio
>
> I'm happy to keep syncing these into m1 for convenience so we don't need
>
+1
On Sun, 2005-07-24 at 12:07 +1000, Brett Porter wrote:
> Hi,
>
> Can I get some opinions on making the following changes to out
> repository policy?
>
> 1) no more snapshots in ibiblio
>
> I'm happy to keep syncing these into m1 for convenience so we don't need
> to change the sync app too m
[ http://jira.codehaus.org/browse/MAVENUPLOAD-431?page=all ]
Nick Faiz updated MAVENUPLOAD-431:
--
Attachment: nlog4j-wrapper-1.2.14.jar
Carlos,
Please find the new nlog4j-wrapper-1.2.14.jar attached to this issue.
It follows your suggestions for repr
On 7/23/05, solo turn <[EMAIL PROTECTED]> wrote:
> somehow i do not understand that, i tried:
>
>
>
> ...
> provided
>
>
> and it still includes it into the war. is this a bug in the war
> plugin?
I don't think so. I have also seen strange behavior with the
dependencies
26 matches
Mail list logo
