Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/10-Jul-2005_12.00.20/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_08.00.19/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_04.00.58/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In my opinion, this thread is not particularly useful. As far as I know,
we have not called for a vote on the final release of Maven 2.0. (we
haven't even released -beta-1 yet, for crying out loud!)
This is my last reply on this thread; it is fast gr
[ http://jira.codehaus.org/browse/MNG-563?page=comments#action_42605 ]
Vincent Massol commented on MNG-563:
Cool. The next step would be to bind the generation to a phase
(generate-sources?) so that running "m2 install" will run it.
> Add generation of
Kris Bravo wrote:
You didn't get my point.
My point was that it is irrelevant if POMs in the repository are minimal or
not.
But it is extremely important that information which is the main maven
repository is _not changing_!!!
I did get your overall point. But contrary to what you're no
[ http://jira.codehaus.org/browse/MNG-563?page=comments#action_42604 ]
Stephane Nicoll commented on MNG-563:
-
Following a chat on IRC:
It's done for 1.3 and 1.4 (no 1.2 though).
use ear:genearte-application-xml
> Add generation of application.xml in EA
Integrate and test the MSN notifier
---
Key: CONTINUUM-215
URL: http://jira.codehaus.org/browse/CONTINUUM-215
Project: Continuum
Type: Task
Reporter: Jason van Zyl
Assigned to: Emmanuel Venisse
Fix For: 1.0-beta-1
The test
Add generation of application.xml in EAR plugin
---
Key: MNG-563
URL: http://jira.codehaus.org/browse/MNG-563
Project: Maven 2
Type: New Feature
Components: maven-plugins
Versions: 2.0-alpha-3
Reporter: Vinc
> You didn't get my point.
>
> My point was that it is irrelevant if POMs in the repository are minimal or
> not.
> But it is extremely important that information which is the main maven
> repository is _not changing_!!!
>
I did get your overall point. But contrary to what you're now saying,
yo
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_12.00.24/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
> -Original Message-
> From: Kris Bravo [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 09, 2005 5:18 PM
> To: Maven Developers List
> Subject: RE: POM issues in the repository
>
> There is nothing wrong with having or using the minimal POMs
> that can be found in the repository. As
[ http://jira.codehaus.org/browse/CONTINUUM-30?page=all ]
Jason van Zyl updated CONTINUUM-30:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Project grouping features
> -
>
> Key: CONTINUUM-30
>
[ http://jira.codehaus.org/browse/CONTINUUM-6?page=all ]
Jason van Zyl updated CONTINUUM-6:
--
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Add security
>
>
> Key: CONTINUUM-6
> URL: http://jira.codehaus
[ http://jira.codehaus.org/browse/CONTINUUM-156?page=all ]
Jason van Zyl updated CONTINUUM-156:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> should validate that an updated pom doesn't change too drastically
> ---
[ http://jira.codehaus.org/browse/CONTINUUM-117?page=all ]
Jason van Zyl updated CONTINUUM-117:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Blame mechanism
> ---
>
> Key: CONTINUUM-117
> URL: http:/
[ http://jira.codehaus.org/browse/CONTINUUM-139?page=all ]
Jason van Zyl updated CONTINUUM-139:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Design per project configuration
>
>
> Key: CO
[ http://jira.codehaus.org/browse/CONTINUUM-145?page=all ]
Jason van Zyl updated CONTINUUM-145:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Allow the creation of template project configurations
>
[ http://jira.codehaus.org/browse/CONTINUUM-127?page=all ]
Jason van Zyl updated CONTINUUM-127:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Try using a series of incorrect data in the integration tests
>
[ http://jira.codehaus.org/browse/CONTINUUM-125?page=all ]
Jason van Zyl updated CONTINUUM-125:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Export/Import projects, configuration and history
>
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=all ]
Jason van Zyl updated CONTINUUM-44:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> multiple profiles
> -
>
> Key: CONTINUUM-44
> URL: http:/
[ http://jira.codehaus.org/browse/CONTINUUM-58?page=all ]
Jason van Zyl updated CONTINUUM-58:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Build all dependent projects.
> -
>
> Key: CONTINUUM-5
[ http://jira.codehaus.org/browse/CONTINUUM-39?page=all ]
Jason van Zyl updated CONTINUUM-39:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> build in the correct order
> --
>
> Key: CONTINUUM-39
>
[ http://jira.codehaus.org/browse/CONTINUUM-66?page=all ]
Jason van Zyl updated CONTINUUM-66:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> m2 install should work for continuum-plexus-application
> -
[ http://jira.codehaus.org/browse/CONTINUUM-137?page=all ]
Jason van Zyl updated CONTINUUM-137:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Store dependency information at the ContinuumProject level
> ---
[ http://jira.codehaus.org/browse/CONTINUUM-69?page=all ]
Jason van Zyl updated CONTINUUM-69:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> Make sure /webapp only contains web resources and not classes.
> --
[ http://jira.codehaus.org/browse/CONTINUUM-143?page=all ]
Jason van Zyl updated CONTINUUM-143:
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> We need to categorize error states and display them useful messages to the
> user
> ---
[ http://jira.codehaus.org/browse/CONTINUUM-93?page=all ]
Jason van Zyl updated CONTINUUM-93:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> setup a public demo site
>
>
> Key: CONTINUUM-93
>
[ http://jira.codehaus.org/browse/CONTINUUM-46?page=all ]
Jason van Zyl updated CONTINUUM-46:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> view the build schedule
> ---
>
> Key: CONTINUUM-46
>
[ http://jira.codehaus.org/browse/CONTINUUM-43?page=all ]
Jason van Zyl updated CONTINUUM-43:
---
Fix Version: (was: 1.0-alpha-3)
1.0-beta-1
> multiple schedules and schedule selection
> -
>
>
[ http://jira.codehaus.org/browse/CONTINUUM-177?page=all ]
Jason van Zyl reassigned CONTINUUM-177:
---
Assign To: Trygve Laugstol
> Include samples of configuration elements in the documenteation
> -
What about taking a play from the Gentoo Portage book? Something similar
to the package masking ~arch keyword might do the trick:
Add an extra tag to the POM schema which indicates whether or not the
POM is stable.
Add a tag in the settings file which indicates whether or not you want
to use unst
There is nothing wrong with having or using the minimal POMs that can be
found in the repository. As a user if I find, for example, a sun library
for which no POM exists, I am willing to submit a basic POM which will
cause my build to continue unimpeded by its absence. I won't however,
stop every t
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_08.00.22/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
Running Maven in a directory not containing a POM file always results in 'Build
Successful'.
Key: MAVEN-1644
URL: http://jira.codehaus.org/browse/MAVEN-1644
Project: maven
T
Errors occurred while performing maven-1 to maven-2 repository conversion.
For more details, see:
http://test.maven.codehaus.org/reports/repoclean/09-Jul-2005_04.00.24/repository.report.txt
-
To unsubscribe, e-mail: [EMAIL PROTE
36 matches
Mail list logo
