We're still waiting for infra to set it up.
On 15/04/2008, at 3:05 AM, Brian E. Fox wrote:
Any chance the archiva TLP has a new notifications list? I seem to get
spammed fairly regularly with massive cascading build failures and
subsequent successful builds. The noise ratio is far too high.
+1 from me.
I tested the staged plugin with the new/fixed configuration options
(columnNames, sortColumnNames, resolutionIds, fixVersionIds,
statusIds, priorityIds) in a commons component and it all looks good.
Thanks for doing this Dennis :)
Niall
On Sun, Apr 13, 2008 at 4:59 PM, Dennis Lundbe
+1
I'm actually using the tasks trying to use them to build trunk instead
of what's there now. I figure the consumption of more dog food is a
good thing.
On 14-Apr-08, at 1:52 PM, Hervé BOUTEMY wrote:
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533
Hi,
We solved 8 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11533&styleName=Html&version=13935
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11533&status=1
Staging repo:
http://people.apache.org/~hboutem
+1
fabrizio
On Sun, Apr 13, 2008 at 5:59 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We solved 17 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=13722
>
> There are still a couple of issues left in JIRA:
>
> http://jira.codehaus
Any chance the archiva TLP has a new notifications list? I seem to get
spammed fairly regularly with massive cascading build failures and
subsequent successful builds. The noise ratio is far too high.
btw the problem is not just let's make the repo work for maven as
there are other consumers out there, ie. Equinox provisioning, that
may like to use the repo as a source and if you change their metadata
to adjust it to maven it wont be useful for them anymore
On Mon, Apr 14, 2008 at 10:44 AM, Car
i gave a talk at eclipsecon covering the subject. You'll need to use
maven 2.0.9+ and force the versions in dependencyManagement
You can find the slides at
http://www.jroller.com/carlossg/entry/slides_from_eclipsecon
On Mon, Apr 14, 2008 at 7:05 AM, Micah Hainline
<[EMAIL PROTECTED]> wrote:
> Hey
At current stage flex-compiler-plugin look at all resources folder
(project.getBuild().getResources()) for configuration files.
Is possible too specify some relative path, such as
.../.../anotherProject/src/main/resources/config.xml
But this has a lot of problems,..
VELO
On Mon, Apr 14, 200
ok. it seems to work then when I change to "generate" goal. However I
would still believe that the "create" goal should also be able to
create the project, but that's just my 2 cents.
I've found other problem with the generate goal though.
When I execute it with network plugged in, everything seem
I think there could be some value to making resource sharing a little
easier out of the box. Naturally it won't fit all instances but those
other instances can already be solved with assembly and or
remote-resources
We currently package up the site descriptor for a parent and that gets
inherited b
Hey Vincent, the qualifiers in the release versions of the Eclipse plugins are
better off stripped out of the repositories in my opinion. Every release
version of the Eclipse platform should have the incremental version number
incremented, so if the community was going to make another release o
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
After an epiphany, I found the problem: A corrupt JAR file in the
repository. I've opened http://jira.codehaus.org/browse/MNG-3523
The bug is still there in 2.0.9. I've downloaded the source and the bug
lurks in this code:
MavenPluginCollector.java
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
The bug is still there in 2.0.9. I've downloaded the source and the bug
lurks in this code:
MavenPluginCollector.java:
public PluginDescriptor getPluginDescriptor( Plugin plugin )
{
// TODO:
You can always use archetype:generate in netbeans integration.
- archetype:create is the same code as in the 1.0-alpha-7 plugin.
- archetype:generate is the new goal but it knows to recognize between
the two formats
and use the associated generator.
Raphaël
2008/4/14, Milos Kleint <[EMAIL PROT
Quoting Aaron Digulla <[EMAIL PROTECTED]>:
The bug is still there in 2.0.9. I've downloaded the source and the
bug lurks in this code:
MavenPluginCollector.java:
public PluginDescriptor getPluginDescriptor( Plugin plugin )
{
// TODO: include version, but can't do this in the
I see.
However it's hard for me to guess which goal shall be run. It means I
need to download the archetype, examine it's content and then execute
the right goal from within the IDE codebase. I guess I could do that
but I think the alpha-1 did somehow manage to figure the difference?
Milos
On Mon
Hi Milos,
Thanks for the feedback.
If the archetype you tried use the archetype-metadata.xml (new
descriptor) instead of the old archetype.xml (1.0-alpha-7 descriptor),
then the goal to call
is mvn archetype:generate. the goal archetype:create is the same as in
the 1.0-alpha-7 version.
I will lo
I've tried with netbeans integration (where alpha-1 works) and it somehow fails.
the debug output is below.
the strange part is this line
Using following parameters for creating OldArchetype: nbm-archetype:1.0.1
the nbm-archetype in question is actually an new archetype, not the old one.
http://re
Hi,
Background:
Trying to mavenize an Eclipse Plugin project, I got error messages
like the following:
Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
I put in jira a test project to reproduce this error [1].
Discussions:
After some investigations:
* the error comes from
+1
Stéphane
On Mon, Apr 14, 2008 at 11:24 AM, Olivier Lamy <[EMAIL PROTECTED]> wrote:
> +1
> --
> Olivier
>
> 2008/4/13, Dennis Lundberg <[EMAIL PROTECTED]>:
>
>
> > Hi,
> >
> > We solved 17 issues:
> >
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&vers
Any one else has tested the plugin?
I have not enough votes for the release.
Regards,
Raphaël
2008/4/14, Jason Dillon <[EMAIL PROTECTED]>:
> +1
>
> ---jason
>
>
>
> On Apr 11, 2008, at 5:22 AM, Raphaël Piéroni wrote:
>
>
> > Hi,
> >
> > We solved 20 issues:
> >
> http://jira.codehaus.org/secur
+1
--
Olivier
2008/4/13, Dennis Lundberg <[EMAIL PROTECTED]>:
> Hi,
>
> We solved 17 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=13722
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
+1
---jason
On Apr 11, 2008, at 5:22 AM, Raphaël Piéroni wrote:
Hi,
We solved 20 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095&styleName=Html&version=14088
Staging repo:
http://people.apache.org/~rafale/archetype-stage-repository/
Staging site:
http://maven.apach
+1
--
Fabrice
- [EMAIL PROTECTED] -
On Sun, Apr 13, 2008 at 5:59 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We solved 17 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=13722
>
> There are still a couple of issues left in JIRA:
>
25 matches
Mail list logo
