Thanks Jesse, worked a treat!
Luke.
Jesse McConnell wrote:
if you are on the new 1.1 versions then just assign System Administrator to
the Guest user and you should be good to go..
assign the Continuum Project Group Administrator to Guest as well
jesse
On 8/10/07, Emmanuel Venisse [EMAIL
Hi guys,
I had a strange problem yesterday, Maven was complaining about an
artifact/dependency in the repository did not exist:
C:\src\mule-2.0-M1\examplesmvn eclipse:eclipse -Dmaven.test.skip=true
-Denforcer.skip=true -o -e
+ Error stacktraces are turned on.
...
[INFO] A required plugin
On 8/12/07, Greg Morgan [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zarick Lau wrote:
You're probably being bitten by http://jira.codehaus.org/browse/PLXCOMP-10.
Thanks! I believe so !!
Someone needs to update the maven-jar-plugin/maven-archiver to use a
Dear users and developers,
While I'm tidy up an multi-module project, I found strange an issue:
In the parent pom, I have an artifact defined with 'optional=true'
within the dependencyManagement:
dependencyManagement
dependencies
dependency
Alright, I got an answer myself. The solution is the add one more 'fileSet'
to include the artifact produced the jar plugin.
fileSet
includes
include${artifactId}-*.jar/include
/includes
directory${basedir}/target/directory
outputDirectorylib/outputDirectory
I have exactly the same problem. I've tried many versions of the wsdl4j
dependency, but I still get that exception.
PeteTh wrote:
I'm trying to use axis2-wsdl2code-maven-plugin with wsdl2code goal.
However I'm getting inconsistencies with class versions, can anyone help?
Has anyone got
Here is the code from the test class that I'm using:
EJB3StandaloneBootstrap.boot(null);
EJB3StandaloneBootstrap.scanClasspath();
HashtableString, String props = new HashtableString,
String();
props.put(java.naming.factory.initial,
Hi,
i have placed some message files in src/main/webapp/WEB-INF/messages/ in order
to use Springs ReloadableResourceBundleMessageSource
No i want to use this property files in a test class:
protected void setUp ( ) throws Exception
{
messageSource = new
As far as I'm concerned, optional doesn't make any sense in
dependencyManagement. So I think what you're seeing is the correct
behavior.
If you want an element to be optional, you need to declare it as such
in the child poms where you declare the dependency (minus version,
which is inherited from
