9:32 p.m.
I keep running into compile errors showing up that do not make sense as
the dependencies for the classes that cannot be found are in the
MAVEN2_CLASSPATH_CONTAINER dependencies. Currently there are errors
related to not being able to resolve the
org/jboss/bootstrap/spi/server/Server
class, even though the classpath contains the
org/jboss/bootstrap/jboss-bootstrap-spi/2.0.0-alpha-2/jboss-bootstrap-spi-2.0.0-alpha-2.jar
I'm also seeing this error for every project it tries to build:
8/10/09 12:04:19 PM PDT: Build errors for testsuite;
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or
missing parameters: [Mojo parameter [name: 'rules'; alias: 'null']] for
mojo: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce
I have tried throwing the workspace away and reimporting it, but that
resulted in the same set of errors. Up to this point some combination of
updating dependencies, rebuilding clean, rebuilding the workspace has
worked, but now it is not.
Anyone else have eclipse working off of the current trunk?
10:22 p.m.
I had some issues as well today. I updated some of the profileservice
tests as some were out of sync with the 5_x branch and had a dependency
on jboss-test, which is not really needed. You might want to try it
again - at least it seems to work for me now.
On 08/10/2009 09:32 PM, Scott Stark wrote:
I keep running into compile errors showing up that do not make sense
as
the dependencies for the classes that cannot be found are in the
MAVEN2_CLASSPATH_CONTAINER dependencies. Currently there are errors
related to not being able to resolve the
org/jboss/bootstrap/spi/server/Server
class, even though the classpath contains the
org/jboss/bootstrap/jboss-bootstrap-spi/2.0.0-alpha-2/jboss-bootstrap-spi-2.0.0-alpha-2.jar
I'm also seeing this error for every project it tries to build:
8/10/09 12:04:19 PM PDT: Build errors for testsuite;
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or
missing parameters: [Mojo parameter [name: 'rules'; alias: 'null']] for
mojo: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce
I have tried throwing the workspace away and reimporting it, but that
resulted in the same set of errors. Up to this point some combination of
updating dependencies, rebuilding clean, rebuilding the workspace has
worked, but now it is not.
Anyone else have eclipse working off of the current trunk?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5:08 a.m.
Ok, I did finally getting working with another clean checkout and import.
Emanuel Muckenhuber wrote:
I had some issues as well today. I updated some of the profileservice
tests as some were out of sync with the 5_x branch and had a
dependency on jboss-test, which is not really needed. You might want
to try it again - at least it seems to work for me now.
10:12 a.m.
Which eclipse versions are you using? Doesn't the latest m2eclipse
require eclipse 3.4.1?
Software update from eclipse 3.4.2 results in the following error
"Cannot find a solution satisfying the following requirements
org.eclipse.debug.ui [3.4.1.v20080811_r341]."
Thanks.
Alexey
Scott Stark wrote:
I keep running into compile errors showing up that do not make sense
as
the dependencies for the classes that cannot be found are in the
MAVEN2_CLASSPATH_CONTAINER dependencies. Currently there are errors
related to not being able to resolve the
org/jboss/bootstrap/spi/server/Server
class, even though the classpath contains the
org/jboss/bootstrap/jboss-bootstrap-spi/2.0.0-alpha-2/jboss-bootstrap-spi-2.0.0-alpha-2.jar
I'm also seeing this error for every project it tries to build:
8/10/09 12:04:19 PM PDT: Build errors for testsuite;
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or
missing parameters: [Mojo parameter [name: 'rules'; alias: 'null']] for
mojo: org.apache.maven.plugins:maven-enforcer-plugin:1.0-beta-1:enforce
I have tried throwing the workspace away and reimporting it, but that
resulted in the same set of errors. Up to this point some combination of
updating dependencies, rebuilding clean, rebuilding the workspace has
worked, but now it is not.
Anyone else have eclipse working off of the current trunk?
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
11:47 a.m.
Scott Stark wrote:
That is the only version showing up when I do an update. Perhaps its
bounded by my not using eclipse 3.4?
yes - the update manager in 3.3 cannot upgrade
your eclipse binary.
Download the Galileo JEE package from eclipse.org and you should be able
to roll.
/max
Max Rydahl Andersen wrote:
>> I'm using
>> eclipse Version: 3.3.2
>> Build id: M20080221-1800
>>
> daaamn! that's like from 2004 ...don't expect m2eclipse to work without
> problems in that version ;)
>
> /max
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>
------------------------------------------------------------------------
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
5359
days inactive
5366
days old
jboss-development@lists.jboss.org
7 comments
4 participants
participants (4)
-
Alexey Loubyansky -
Emanuel Muckenhuber -
Max Rydahl Andersen -
Scott Stark