date:20060927

Re: rbac-integration continuum branch

2006-09-27 Thread Jason van Zyl


+1 !!!

Nice work!

On 28 Sep 06, at 3:58 AM 28 Sep 06, Jesse McConnell wrote:


Over the course of the past 3 weeks I've worked with joakim on the
plexus-security effort to bring rbac based security to Archiva.
We succeeded.

Last Friday (or so) I took the continuum/trunk and created the
rbac-integration branch.
I wanted from to test the integration of rbac based security, using
the plexus-security project, into continuum.

It integrated beautifully, without a whole lot of work, in record
time, and is pretty functional now ...

Some of the fun things that plexus-security brings with it are:

* full separation between application webapp and security (lightweight
integration).
* proper modularization for security components (authentication,
authorization, policy, system, web, etc...)
* rbac (role based access control) authorization provider.
* full user management war overlay (using healthy chunk of maven-user
to make it happen)
* toggle-able guest user authorization.
* remember me and single sign on authentication.
* forced admin account creation (through use of interceptor)
* key based authentication (remember me, single sign on, new user
validation emails, and password resets).
* http auth filters (basic and digest).
* aggressive plexus utilization.
* aggressive xwork / webwork integration.
* xwork interceptors for force admin, auto login (remember me),
secured action, and environment checks.
* secured actions for all of the /security namespace and at least one
continuum secured action (these are enforced by the
pssSecureActionInterceptor)
* all the password validation, user management stuff (again maven- 
user origins)

* continuum-security artifact containing the actual static and dynamic
roles, and a continuum role manager that merges permissions to the
core system, user, and guest users
* ifAuthorized, ifAnyAuthorized, elseAuthorized jsp tags.
* placeholders for ldap authentication, authorization and user details
retrieval using plexus ldap components
* ability to re-use Acegi for authentication

I think it is very usable now, its a matter of some jsp and action
work to clean up some things and hide some other knobs and buttons.

I'd like to get feedback and discussion from the others here about the
implementation, and consider a vote to merge it to trunk after that. I
believe it is stable enough to move forward with.

jesse

--
jesse mcconnell
[EMAIL PROTECTED]

Re: svn commit: r450539 - in /maven/components/branches/maven-2.1-jvz: maven.ipr maven.iws

2006-09-27 Thread Jason van Zyl



On 27 Sep 06, at 8:34 PM 27 Sep 06, [EMAIL PROTECTED] wrote:


Author: jvanzyl
Date: Wed Sep 27 11:34:50 2006
New Revision: 450539

URL: http://svn.apache.org/viewvc?view=rev&rev=450539
Log: (empty)

Modified:
maven/components/branches/maven-2.1-jvz/maven.ipr
maven/components/branches/maven-2.1-jvz/maven.iws




I have modified my svn configuration locally to omit all this crap. I  
asked around #asfinfra and apparently you can recursively set a  
property. So you can't set the svn:ignore property once which seems  
really crappy. With it in my svn configuration I shouldn't be spewing  
to the list but there has to be a way to do this consistently for a  
repository once, it's just silly everyone has to remember this stupid  
command every time they create a new directory, or have to edit their  
configuration. It should be built into the repository.


Thanks,

Jason. 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

BUILD FAILED.../maven-java-plugin-1.5/plugin.jelly

2006-09-27 Thread charles magnes


Hello,
Could anybody help me about some troubles I encountered when I tried to run:
'maven buildall' on an Ubuntu os.
I received the following message:

**
[EMAIL PROTECTED]:~/agila/trunk/modules/bpel$ maven buildall
__  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Tag library requested that is not present: 'maven' in plugin: 'null'
Starting the reactor...
Our processing order:
Agila Common
Agila Engine Common
Agila Engine Client
Agila User/Group/Role Manager
Agila WorkList Manager
Agila Engine
Agila Deployer
Agila Distro
Agila Web Services
Agila Web Applications
+
| Building Agila Common
| Memory: 3M/6M
+
Tag library requested that is not present: 'maven' in plugin: 'null'
build:start:

buildall:
build:start:

clean:clean:
   [delete] Deleting directory 
/home/clasie/agila/trunk/modules/bpel/common/target

Tag library requested that is not present: 'maven' in plugin: 'null'

clean:

buildmodule:
java:prepare-filesystem:
   [mkdir] Created dir: 
/home/clasie/agila/trunk/modules/bpel/common/target/classes


java:compile:
   [copy] Copying 1 file to 
/home/clasie/agila/trunk/modules/bpel/common/target/classes
   [echo] Compiling to 
/home/clasie/agila/trunk/modules/bpel/./common/target/classes

   [echo]
==

 NOTE: Targetting JVM 1.5, classes
 will not run on earlier JVMs

==

   [javac] Compiling 12 source files to 
/home/clasie/agila/trunk/modules/bpel/common/target/classes
error: error reading 
/home/clasie/.maven/repository/jboss/jars/jboss-aop-1.0b2.jar; error in 
opening zip file
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:18: 
package org.jboss.aop.advice does not exist

import org.jboss.aop.advice.Interceptor;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:19: 
package org.jboss.aop.joinpoint does not exist

import org.jboss.aop.joinpoint.Invocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:20: 
package org.jboss.aop.joinpoint does not exist

import org.jboss.aop.joinpoint.MethodInvocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:28: 
cannot find symbol

symbol: class Interceptor
public class LoggingInterceptor implements Interceptor {
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:36: 
cannot find symbol

symbol  : class Invocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   public Object invoke(Invocation invocation) throws Throwable {
^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37: 
cannot find symbol

symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37: 
cannot find symbol

symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
  ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors

BUILD FAILED
File.. /home/clasie/agila/trunk/modules/bpel/maven.xml
Element... maven:reactor
Line.. 16
Column 78
Unable to obtain goal [buildmodule] -- 
/home/clasie/.maven/cache/maven-java-plugin-1.5/plugin.jelly:63:48: 
 Compile failed; see the compiler error output for details.

Total time: 27 seconds
Finished at: Wed Sep 27 15:55:10 CEST 2006
*

Many thanks for any help.

Claude
[EMAIL PROTECTED]

_
Ping Pong Ping Pong 4 mails déjà ! Arrêtez de perdre votre temps grâce à 
Windows Live Messenger ! http://get.live.com/messenger/overview



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Subscription: Outstanding Repository Maintenance: Uploads

2006-09-27 Thread jira

Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (36 issues)
Subscriber: mavendevlist


Key Summary
MAVENUPLOAD-1156Please upload HSQLDB 1.8.0.7
http://jira.codehaus.org/browse/MAVENUPLOAD-1156
MAVENUPLOAD-1155Spring modules 0.6 bundles
http://jira.codehaus.org/browse/MAVENUPLOAD-1155
MAVENUPLOAD-1154WSDL4J 1.6.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1154
MAVENUPLOAD-1153Please upload MessAdmin 4.0
http://jira.codehaus.org/browse/MAVENUPLOAD-1153
MAVENUPLOAD-1152Upload log4j 1.2.14 release
http://jira.codehaus.org/browse/MAVENUPLOAD-1152
MAVENUPLOAD-1121Jericho HTML Parser 2.3
http://jira.codehaus.org/browse/MAVENUPLOAD-1121
MAVENUPLOAD-1053Upload hibernate-tools 3.2.0-beta6
http://jira.codehaus.org/browse/MAVENUPLOAD-1053
MAVENUPLOAD-1151Please upload objectlabkit version 1.0.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1151
MAVENUPLOAD-1150Java2html 5.0 upload
http://jira.codehaus.org/browse/MAVENUPLOAD-1150
MAVENUPLOAD-1149Upload jboss-seam-ui-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1149
MAVENUPLOAD-1148Upload jboss-seam-debug-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1148
MAVENUPLOAD-1147Upload jboss-seam-1.0.1.jar
http://jira.codehaus.org/browse/MAVENUPLOAD-1147
MAVENUPLOAD-1146JasperReports 1.2.7 upload
http://jira.codehaus.org/browse/MAVENUPLOAD-1146
MAVENUPLOAD-1145JIntellitype 1.0
http://jira.codehaus.org/browse/MAVENUPLOAD-1145
MAVENUPLOAD-1143Upload Echo2 2.1.0.beta5 (corrected groupId)
http://jira.codehaus.org/browse/MAVENUPLOAD-1143
MAVENUPLOAD-1144Upload Echo2-Extras 0.3 (corrected groupId)
http://jira.codehaus.org/browse/MAVENUPLOAD-1144
MAVENUPLOAD-1134Upload net.sf.oval_0.6
http://jira.codehaus.org/browse/MAVENUPLOAD-1134
MAVENUPLOAD-1133Upload wsdl4j-1.5.3
http://jira.codehaus.org/browse/MAVENUPLOAD-1133
MAVENUPLOAD-1104Elmo 3.0
http://jira.codehaus.org/browse/MAVENUPLOAD-1104
MAVENUPLOAD-1130Rhino js-1.5R4.1
http://jira.codehaus.org/browse/MAVENUPLOAD-1130
MAVENUPLOAD-1128Rhino js-1.5R3
http://jira.codehaus.org/browse/MAVENUPLOAD-1128
MAVENUPLOAD-978Upload ejb-3.0-public-draft-20060502 (needed for hibernate)
http://jira.codehaus.org/browse/MAVENUPLOAD-978
MAVENUPLOAD-1129Rhino js-1.5R4-RC3
http://jira.codehaus.org/browse/MAVENUPLOAD-1129
MAVENUPLOAD-1084Upload drools:drools-core:3.0.4 to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-1084
MAVENUPLOAD-1088Upload drools:drools-decisiontables:3.0.4 to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-1088
MAVENUPLOAD-1085Upload drools:drools-compiler:3.0.4 to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-1085
MAVENUPLOAD-1090Upload of Maven Docbkx Plugin
http://jira.codehaus.org/browse/MAVENUPLOAD-1090
MAVENUPLOAD-1087Upload drools:drools-jsr94:3.0.4 to ibiblio
http://jira.codehaus.org/browse/MAVENUPLOAD-1087
MAVENUPLOAD-1059j2ssh (sshtools) 0.2.7
http://jira.codehaus.org/browse/MAVENUPLOAD-1059
MAVENUPLOAD-1055Please Upload Registry J2SE
http://jira.codehaus.org/browse/MAVENUPLOAD-1055
MAVENUPLOAD-1060jstl-1.2.jar corrupt
http://jira.codehaus.org/browse/MAVENUPLOAD-1060
MAVENUPLOAD-1056Please Upload Registry J2EE
http://jira.codehaus.org/browse/MAVENUPLOAD-1056
MAVENUPLOAD-1033Please upload JBoss Cache Version 1.4.0
http://jira.codehaus.org/browse/MAVENUPLOAD-1033
MAVENUPLOAD-1008Full bundle for xerces:dom3-xml-apis:1.0
http://jira.codehaus.org/browse/MAVENUPLOAD-1008
MAVENUPLOAD-976Please upload SUN Java 1.2 rutime 
http://jira.codehaus.org/browse/MAVENUPLOAD-976
MAVENUPLOAD-789Tomcat 5.5.15 poms for existing jars
http://jira.codehaus.org/browse/MAVENUPLOAD-789


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

2006-09-27 Thread jira

Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (30 issues)
Subscriber: mavendevlist


Key Summary
MEV-450 plexus-velocity 1.1.2 includes invalid external snapshot 
repositories
http://jira.codehaus.org/browse/MEV-450
MEV-449 lucene 1.9.1 JAR is hosed.
http://jira.codehaus.org/browse/MEV-449
MEV-448 xmlrpc POM should include commons-codec
http://jira.codehaus.org/browse/MEV-448
MEV-392 bad dependencies in commons-logging-1.1.pom
http://jira.codehaus.org/browse/MEV-392
MEV-443 Several projects have maven-metadata.xml files that are missing 
released versions
http://jira.codehaus.org/browse/MEV-443
MEV-441 Several projects have bad maven-metadata.xml files that are 
screwing up dependencies with version range feature
http://jira.codehaus.org/browse/MEV-441
MEV-20  clean up bad IDs in the repository
http://jira.codehaus.org/browse/MEV-20
MEV-436 JOTM 2.0.10 incorrectly specifies javax.resource/connector-1.0 it 
needs connector-1.5.
http://jira.codehaus.org/browse/MEV-436
MEV-427 relocate ehcache:ehcache to net.sf.ehcache
http://jira.codehaus.org/browse/MEV-427
MEV-296 Activemq-core (and other activemq projects) 3.2.1 have unexpanded 
variables
http://jira.codehaus.org/browse/MEV-296
MEV-405 pom for cactus:cactus:13-1.7.2
http://jira.codehaus.org/browse/MEV-405
MEV-404 pom for cactus:cactus-ant:13-1.7.2
http://jira.codehaus.org/browse/MEV-404
MEV-401 Incoherences / duplication between javax.xml and com.sun.xml
http://jira.codehaus.org/browse/MEV-401
MEV-334 Stax POM points to an invalid XMLBeans dependency
http://jira.codehaus.org/browse/MEV-334
MEV-384 velocity 1.4 dependencies are wrong
http://jira.codehaus.org/browse/MEV-384
MEV-375 Relocate xpp to xpp3
http://jira.codehaus.org/browse/MEV-375
MEV-364 Fix dependencies of common-lang 1.0 (add test scope for junit)
http://jira.codehaus.org/browse/MEV-364
MEV-352 Relocate cvslib in netbeans groupId to cvsclient in org.netbeans.lib
http://jira.codehaus.org/browse/MEV-352
MEV-356 Missing dep on jboss-common in jbossmq-client & jnp-client 4.0.2
http://jira.codehaus.org/browse/MEV-356
MEV-351 xmlc-xerces-2.2.7.1.jar is unnecessary and  xmlc-apis.jar is 
required.
http://jira.codehaus.org/browse/MEV-351
MEV-330 WebWork 2.2.1 POM should list FreeMarker as a dependency since it's 
required for plain ol' JSPs
http://jira.codehaus.org/browse/MEV-330
MEV-325 Description of jaxb-api 1.0.1 is wrong
http://jira.codehaus.org/browse/MEV-325
MEV-320 Hibernate 3.1.x POMs pull in Sun jars
http://jira.codehaus.org/browse/MEV-320
MEV-201 should have dependency on org.relaxngdatatype.relaxngDatatype
http://jira.codehaus.org/browse/MEV-201
MEV-173 xmlpull JARs exist in two different places on ibiblio
http://jira.codehaus.org/browse/MEV-173
MEV-48  openejb poms
http://jira.codehaus.org/browse/MEV-48
MEV-45  Full list of poms that doesn't respect the m2 format
http://jira.codehaus.org/browse/MEV-45
MEV-36  Exo POM(s) missing dependency versions
http://jira.codehaus.org/browse/MEV-36
MEV-33  XOM POM references xercesImpl v.2.2.1 which does not exist in repo
http://jira.codehaus.org/browse/MEV-33
MEV-31  XOM POM references xmlParserAPIs v2.6.1 which is not in the repo
http://jira.codehaus.org/browse/MEV-31


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: trouble in building maven

2006-09-27 Thread Wayne Fay


This question is not appropriate for the Maven Dev list and I doubt
you'll receive a response.

Please send it to Maven Users, or even better, directly to the Agila
Users/Dev list as this is really "their" problem.

Wayne

On 9/27/06, charles magnes <[EMAIL PROTECTED]> wrote:

Hello,
Could anybody help me about some troubles I encountered when I tried to run:
'maven buildall' on an Ubuntu os.
I received the following message:

**
[EMAIL PROTECTED]:~/agila/trunk/modules/bpel$ maven buildall
__  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Tag library requested that is not present: 'maven' in plugin: 'null'
Starting the reactor...
Our processing order:
Agila Common
Agila Engine Common
Agila Engine Client
Agila User/Group/Role Manager
Agila WorkList Manager
Agila Engine
Agila Deployer
Agila Distro
Agila Web Services
Agila Web Applications
+
| Building Agila Common
| Memory: 3M/6M
+
Tag library requested that is not present: 'maven' in plugin: 'null'
build:start:

buildall:
build:start:

clean:clean:
   [delete] Deleting directory
/home/clasie/agila/trunk/modules/bpel/common/target
Tag library requested that is not present: 'maven' in plugin: 'null'

clean:

buildmodule:
java:prepare-filesystem:
   [mkdir] Created dir:
/home/clasie/agila/trunk/modules/bpel/common/target/classes

java:compile:
   [copy] Copying 1 file to
/home/clasie/agila/trunk/modules/bpel/common/target/classes
   [echo] Compiling to
/home/clasie/agila/trunk/modules/bpel/./common/target/classes
   [echo]
==

 NOTE: Targetting JVM 1.5, classes
 will not run on earlier JVMs

==

   [javac] Compiling 12 source files to
/home/clasie/agila/trunk/modules/bpel/common/target/classes
error: error reading
/home/clasie/.maven/repository/jboss/jars/jboss-aop-1.0b2.jar; error in
opening zip file
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:18:
package org.jboss.aop.advice does not exist
import org.jboss.aop.advice.Interceptor;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:19:
package org.jboss.aop.joinpoint does not exist
import org.jboss.aop.joinpoint.Invocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:20:
package org.jboss.aop.joinpoint does not exist
import org.jboss.aop.joinpoint.MethodInvocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:28:
cannot find symbol
symbol: class Interceptor
public class LoggingInterceptor implements Interceptor {
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:36:
cannot find symbol
symbol  : class Invocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   public Object invoke(Invocation invocation) throws Throwable {
^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37:
cannot find symbol
symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37:
cannot find symbol
symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
  ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors

BUILD FAILED
File.. /home/clasie/agila/trunk/modules/bpel/maven.xml
Element... maven:reactor
Line.. 16
Column 78
Unable to obtain goal [buildmodule] --
/home/clasie/.maven/cache/maven-java-plugin-1.5/plugin.jelly:63:48:
 Compile failed; see the compiler error output for details.
Total time: 27 seconds
Finished at: Wed Sep 27 15:55:10 CEST 2006
**

Many thanks for any help.

Claude
[EMAIL PROTECTED]

_
Qui sont les vrais amis de vos amis ? Découvrez-les sur Windows Live Spaces
! http://spaces.live.com/default.aspx?page=Ed01&ss=False


-
To unsubscribe, e-mail

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

2006-09-27 Thread Brett Porter

I really don't know how you are going to provision the toolchains  
without something in the settings which means core changes, but I'll  
see what you come up with.


I'm not sure about using properties in that fashion, really - maybe  
this is just a change to a simpler plugin configuration for now, and  
then a POM element can be introduced in 2.1 that removes the need for  
any plugin configuration when it is set at a project level?


- Brett

On 28/09/2006, at 4:21 AM, Jason van Zyl wrote:



On 27 Sep 06, at 2:50 PM 27 Sep 06, Brett Porter wrote:

not always the way we've done it, but I wonder if these should  
start in the sandbox?


Regardless - won't this require POM changes making it depend on 2.1?



No, not if we standardize on a common property as a transition  
which can be a general strategy for a lot of new POM elements like  
categories and tags.


Jason.


- Brett

On 27/09/2006, at 10:41 PM, [EMAIL PROTECTED] wrote:


Author: jvanzyl
Date: Wed Sep 27 05:41:42 2006
New Revision: 450421

URL: http://svn.apache.org/viewvc?view=rev&rev=450421
Log: (empty)

Added:
maven/shared/trunk/maven-toolchain/
  - copied from r450379, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/

maven/shared/trunk/maven-toolchain/pom.xml
  - copied unchanged from r450409, maven/components/branches/ 
maven-2.1-jvz/maven-toolchain/pom.xml

maven/shared/trunk/maven-toolchain/src/
  - copied from r450409, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/src/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Jason van Zyl
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r450387 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.iws

2006-09-27 Thread Jason van Zyl



On 27 Sep 06, at 2:22 PM 27 Sep 06, Brett Porter wrote:



On 27/09/2006, at 7:28 PM, [EMAIL PROTECTED] wrote:



+//versions where you have things like 1.4_003 and 1.5_006


what's the issue here?


The general specification like 1.5 in theory should be fine most of  
the time, but the specific version is used to find bugs or work  
around bugs. Building with one version of a JDK and something  
working, while in the next release it does not. You might have  
profiles that use every possible version of JavaToolChain you can to  
test thoroughly so we might end up one's for each version so we just  
have to account for each version and have a way to point to it  
specifically when someone has all versions of JDK 1.5 for example.





+//app servers possibly


That seems like a separate kettle of fish.



Yup, some netbeans folks straightened me out.


- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Jason van Zyl
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

2006-09-27 Thread Jason van Zyl



On 27 Sep 06, at 2:50 PM 27 Sep 06, Brett Porter wrote:

not always the way we've done it, but I wonder if these should  
start in the sandbox?


Regardless - won't this require POM changes making it depend on 2.1?



No, not if we standardize on a common property as a transition which  
can be a general strategy for a lot of new POM elements like  
categories and tags.


Jason.


- Brett

On 27/09/2006, at 10:41 PM, [EMAIL PROTECTED] wrote:


Author: jvanzyl
Date: Wed Sep 27 05:41:42 2006
New Revision: 450421

URL: http://svn.apache.org/viewvc?view=rev&rev=450421
Log: (empty)

Added:
maven/shared/trunk/maven-toolchain/
  - copied from r450379, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/

maven/shared/trunk/maven-toolchain/pom.xml
  - copied unchanged from r450409, maven/components/branches/ 
maven-2.1-jvz/maven-toolchain/pom.xml

maven/shared/trunk/maven-toolchain/src/
  - copied from r450409, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/src/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Jason van Zyl
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r450383 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.ipr maven.iws

2006-09-27 Thread Jason van Zyl


On 27 Sep 06, at 2:21 PM 27 Sep 06, Brett Porter wrote:


Do we need a hierachy of interfaces? JavaToolchain?



Milos and I started with the way Netbeans does this and I think it's  
fairly accurate and is working for them. I think what the IDEs do is  
very close, if not exactly what we are trying to achieve. We're  
mocking it all up with some plugins, I'll put it in the queue and in  
the wiki.


Jason van Zyl
[EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

trouble in building maven

2006-09-27 Thread charles magnes


Hello,
Could anybody help me about some troubles I encountered when I tried to run:
'maven buildall' on an Ubuntu os.
I received the following message:

**
[EMAIL PROTECTED]:~/agila/trunk/modules/bpel$ maven buildall
__  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Tag library requested that is not present: 'maven' in plugin: 'null'
Starting the reactor...
Our processing order:
Agila Common
Agila Engine Common
Agila Engine Client
Agila User/Group/Role Manager
Agila WorkList Manager
Agila Engine
Agila Deployer
Agila Distro
Agila Web Services
Agila Web Applications
+
| Building Agila Common
| Memory: 3M/6M
+
Tag library requested that is not present: 'maven' in plugin: 'null'
build:start:

buildall:
build:start:

clean:clean:
   [delete] Deleting directory 
/home/clasie/agila/trunk/modules/bpel/common/target

Tag library requested that is not present: 'maven' in plugin: 'null'

clean:

buildmodule:
java:prepare-filesystem:
   [mkdir] Created dir: 
/home/clasie/agila/trunk/modules/bpel/common/target/classes


java:compile:
   [copy] Copying 1 file to 
/home/clasie/agila/trunk/modules/bpel/common/target/classes
   [echo] Compiling to 
/home/clasie/agila/trunk/modules/bpel/./common/target/classes

   [echo]
==

 NOTE: Targetting JVM 1.5, classes
 will not run on earlier JVMs

==

   [javac] Compiling 12 source files to 
/home/clasie/agila/trunk/modules/bpel/common/target/classes
error: error reading 
/home/clasie/.maven/repository/jboss/jars/jboss-aop-1.0b2.jar; error in 
opening zip file
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:18: 
package org.jboss.aop.advice does not exist

import org.jboss.aop.advice.Interceptor;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:19: 
package org.jboss.aop.joinpoint does not exist

import org.jboss.aop.joinpoint.Invocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:20: 
package org.jboss.aop.joinpoint does not exist

import org.jboss.aop.joinpoint.MethodInvocation;
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:28: 
cannot find symbol

symbol: class Interceptor
public class LoggingInterceptor implements Interceptor {
  ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:36: 
cannot find symbol

symbol  : class Invocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   public Object invoke(Invocation invocation) throws Throwable {
^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37: 
cannot find symbol

symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
   ^
/home/clasie/agila/trunk/modules/bpel/common/src/java/org/apache/agila/bpel/common/aspect/LoggingInterceptor.java:37: 
cannot find symbol

symbol  : class MethodInvocation
location: class org.apache.agila.bpel.common.aspect.LoggingInterceptor
   MethodInvocation mi = (MethodInvocation) invocation;
  ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
8 errors

BUILD FAILED
File.. /home/clasie/agila/trunk/modules/bpel/maven.xml
Element... maven:reactor
Line.. 16
Column 78
Unable to obtain goal [buildmodule] -- 
/home/clasie/.maven/cache/maven-java-plugin-1.5/plugin.jelly:63:48: 
 Compile failed; see the compiler error output for details.

Total time: 27 seconds
Finished at: Wed Sep 27 15:55:10 CEST 2006
**

Many thanks for any help.

Claude
[EMAIL PROTECTED]

_
Qui sont les vrais amis de vos amis ? Découvrez-les sur Windows Live Spaces 
! http://spaces.live.com/default.aspx?page=Ed01&ss=False



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

2006-09-27 Thread Brett Porter

not always the way we've done it, but I wonder if these should start  
in the sandbox?


Regardless - won't this require POM changes making it depend on 2.1?

- Brett

On 27/09/2006, at 10:41 PM, [EMAIL PROTECTED] wrote:


Author: jvanzyl
Date: Wed Sep 27 05:41:42 2006
New Revision: 450421

URL: http://svn.apache.org/viewvc?view=rev&rev=450421
Log: (empty)

Added:
maven/shared/trunk/maven-toolchain/
  - copied from r450379, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/

maven/shared/trunk/maven-toolchain/pom.xml
  - copied unchanged from r450409, maven/components/branches/ 
maven-2.1-jvz/maven-toolchain/pom.xml

maven/shared/trunk/maven-toolchain/src/
  - copied from r450409, maven/components/branches/maven-2.1- 
jvz/maven-toolchain/src/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r449533 [1/3] - in /maven/continuum/trunk: ./ continuum-api/src/main/java/org/apache/maven/continuum/ continuum-api/src/main/java/org/apache/maven/continuum/project/builder/ continuum-

2006-09-27 Thread Brett Porter

On 27/09/2006, at 9:45 AM, Carlos Sanchez wrote:

Thanks forthe check, my eyes were hurting after i finished with  
this ;)

:)

> -ProjectGroup getDefaultProjectGroup()
> -throws ContinuumStoreException;
> -

was this intentional?

where is this?

Continuum interface. I think it might have been intentional since the  
project groups have changed, but thought I'd check.

persistence layer exceptions should not be catched if not doing
anything, so they can be handled in upper levels or just cause an
internal error.
For instance a ObjectNotFound could mean to the web layer that the
object was deleted while the user was reading the page.

Ok. I'm not sure I agree with the technique of exception handling  
(why would the web interface understand what an "object not found  
exception" is?) - but that's a different topic for later.

Yes, that should be done, still I like the filter so I can use a
different db for development avoiding conficts in application.xml

You can do that with the data source by changing your appserver/jetty  
plugin config at will.

- Brett

Re: svn commit: r450387 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.iws

2006-09-27 Thread Brett Porter



On 27/09/2006, at 7:28 PM, [EMAIL PROTECTED] wrote:



+//versions where you have things like 1.4_003 and 1.5_006


what's the issue here?


+//app servers possibly


That seems like a separate kettle of fish.

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: svn commit: r450379 - in /maven/components/branches/maven-2.1-jvz: ./ maven-toolchain/ maven-toolchain/src/ maven-toolchain/src/main/ maven-toolchain/src/main/java/ maven-toolchain/src/main/java/o

2006-09-27 Thread Brett Porter

can yu remove your IDEA files and ignore them? They make a lot of  
noise in commits.


Thanks,
Brett


On 27/09/2006, at 6:41 PM, [EMAIL PROTECTED] wrote:


Author: jvanzyl
Date: Wed Sep 27 01:41:10 2006
New Revision: 450379

URL: http://svn.apache.org/viewvc?view=rev&rev=450379
Log:
adding toolchain interface and milos is going to add some stuff  
using netbeans toolchain definitions


Added:
maven/components/branches/maven-2.1-jvz/maven-toolchain/
maven/components/branches/maven-2.1-jvz/maven-toolchain/ 
pom.xml   (with props)

maven/components/branches/maven-2.1-jvz/maven-toolchain/src/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/main/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/maven/
maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/maven/Toolchain.java   (with props)

Modified:
maven/components/branches/maven-2.1-jvz/maven.ipr
maven/components/branches/maven-2.1-jvz/maven.iws
maven/components/branches/maven-2.1-jvz/pom.xml

Added: maven/components/branches/maven-2.1-jvz/maven-toolchain/pom.xml
URL: http://svn.apache.org/viewvc/maven/components/branches/ 
maven-2.1-jvz/maven-toolchain/pom.xml?view=auto&rev=450379
== 

--- maven/components/branches/maven-2.1-jvz/maven-toolchain/pom.xml  
(added)
+++ maven/components/branches/maven-2.1-jvz/maven-toolchain/pom.xml  
Wed Sep 27 01:41:10 2006

@@ -0,0 +1,21 @@
+
+  
+maven
+org.apache.maven
+2.1-SNAPSHOT
+  
+  4.0.0
+  org.apache.maven
+  maven-toolchain
+  Maven Toolchain
+  1.0-SNAPSHOT
+  http://maven.apache.org
+  
+
+  junit
+  junit
+  3.8.1
+  test
+
+  
+

Propchange: maven/components/branches/maven-2.1-jvz/maven-toolchain/ 
pom.xml
-- 


svn:eol-style = native

Propchange: maven/components/branches/maven-2.1-jvz/maven-toolchain/ 
pom.xml
-- 


svn:keywords = "Author Date Id Revision"

Added: maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/maven/Toolchain.java
URL: http://svn.apache.org/viewvc/maven/components/branches/ 
maven-2.1-jvz/maven-toolchain/src/main/java/org/apache/maven/ 
Toolchain.java?view=auto&rev=450379
== 

--- maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/maven/Toolchain.java (added)
+++ maven/components/branches/maven-2.1-jvz/maven-toolchain/src/ 
main/java/org/apache/maven/Toolchain.java Wed Sep 27 01:41:10 2006

@@ -0,0 +1,10 @@
+package org.apache.maven;
+
+/**
+ * @author Jason van Zyl
+ */
+public interface Toolchain
+{
+//classpath
+//path to binaries
+}

Propchange: maven/components/branches/maven-2.1-jvz/maven-toolchain/ 
src/main/java/org/apache/maven/Toolchain.java
-- 


svn:eol-style = native

Propchange: maven/components/branches/maven-2.1-jvz/maven-toolchain/ 
src/main/java/org/apache/maven/Toolchain.java
-- 


svn:keywords = "Author Date Id Revision"

Modified: maven/components/branches/maven-2.1-jvz/maven.ipr
URL: http://svn.apache.org/viewvc/maven/components/branches/ 
maven-2.1-jvz/maven.ipr?view=diff&rev=450379&r1=450378&r2=450379
== 


--- maven/components/branches/maven-2.1-jvz/maven.ipr (original)
+++ maven/components/branches/maven-2.1-jvz/maven.ipr Wed Sep 27  
01:41:10 2006

@@ -287,6 +287,7 @@
   
   
   
+  
   

 
   
@@ -300,7 +301,10 @@
 
   
   
-  
+  
+/Users/jvanzyl/js/org/ 
codehaus/plexus/trunk/plexus-sandbox/plexus-classworlds/src/test/ 
java/org/codehaus/classworlds/configuratorSourceSafePersistencyRemovedFolder>
+/Users/jvanzyl/js/org/ 
codehaus/plexus/trunk/plexus-sandbox/plexus-classworlds/src/main/ 
java/org/codehaus/classworlds/configuratorSourceSafePersistencyRemovedFolder>

+  
   
 
   

Modified: maven/components/branches/maven-2.1-jvz/maven.iws
URL: http://svn.apache.org/viewvc/maven/components/branches/ 
maven-2.1-jvz/maven.iws?view=diff&rev=450379&r1=450378&r2=450379
== 


--- maven/components/branches/maven-2.1-jvz/maven.iws (original)
+++ maven/components/branches/maven-2.1-jvz/maven.iws Wed Sep 27  
01:41:10 2006

@@ -17,15 +17,8 @@

Re: checkout, edit and synergy

2006-09-27 Thread Julien Henry



Hi,

I get help from a Synergy user, and he said using Synergy checkout 
command is not a problem. Indeed, even if a new version is created for 
each checkout, it's a "working" (Synergy state) version that is not 
visible for other developpers (and could be deleted later).


Now I have a new problem. When you ask Synergy to checkout project 
foo~1.0 in "target/checkout" folder, your pom is in 
"taget/checkout/foo~1.0/foo/pom.xml". I know scm:bootstrap and Continuum 
expect the pom to be in the root of checkout directory, and I'm not sure 
how to solve this.


I ask some Synergy guru about getting only the content of project 
directory (I'm waiting for an answer), but if it is not possible, 
perhaps can we add a new parameter in CheckOutScmResult that store where 
is the root pom.xml. This will require to patch tools using checkout 
command. For scm plugin, it will not be difficult (only change working 
dir), but I don't know what is the amount of work for Continuum.


Any suggestion ?

++

Julien

Julien Henry a écrit :


Hi,

I have another problem with Synergy scm plugin. Here is what is 
already done:


"working dir" $> mvn scm:checkout 
-DconnectionUrl=scm:synergy:myProjet~1.0

run the following ccm commands :
ccm start ...
ccm wa -set "working dir" -pst %project_name myProjet~1.0
ccm sync -r -p myProjet~1.0
ccm stop

I think it is what we can expect from maven checkout command, that is 
to say get a specified version of a project in a specified directory.
The problem is that Synergy is a "locking" scm. You can't edit/add 
file if you don't checkout project before (take care, it is the 
Synergy meaning of checkout !). But the Synergy checkout command not 
only allow you to edit files, but increments project version in 
database. It is the opposite of SVN where revision is incremented 
after checkin.


When you are in a locked directory, and you want to edit a file, I 
don't know what ccm command to run. If someone using CM/Synergy could 
help me, it would be great !


I'm considering calling ccm checkout in the "maven" checkout, but:
1) I had to update the POM because the version of the checkout project 
is incremented
2) If continuum perform a checkout each night, this will create a 
great number of version in the database, and lock the project (AFAIK)


Thanks for any idea.


--

_

Julien HENRY | **Capgemini Sud **| Nice

www.fr.capgemini.com 

Porte de l’Arénas – Entrée B | 455 Promenade des Anglais | 06200 Nice



**Join the Collaborative Business Experience **
_



This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient,  you are not authorized 
to read, print, retain, copy, disseminate,  distribute, or use this message or 
any part thereof. If you receive this  message in error, please notify the 
sender immediately and delete all  copies of this message.

Re: rbac-integration continuum branch

Re: svn commit: r450539 - in /maven/components/branches/maven-2.1-jvz: maven.ipr maven.iws

BUILD FAILED.../maven-java-plugin-1.5/plugin.jelly

[jira] Subscription: Outstanding Repository Maintenance: Uploads

[jira] Subscription: Outstanding Repository Maintenance: Evangelism

Re: trouble in building maven

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Re: svn commit: r450387 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.iws

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Re: svn commit: r450383 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.ipr maven.iws

trouble in building maven

Re: svn commit: r450421 - in /maven/shared/trunk/maven-toolchain: ./ pom.xml src/

Re: svn commit: r449533 [1/3] - in /maven/continuum/trunk: ./ continuum-api/src/main/java/org/apache/maven/continuum/ continuum-api/src/main/java/org/apache/maven/continuum/project/builder/ continuum-

Re: svn commit: r450387 - in /maven/components/branches/maven-2.1-jvz: maven-toolchain/src/main/java/org/apache/maven/Toolchain.java maven.iws

Re: svn commit: r450379 - in /maven/components/branches/maven-2.1-jvz: ./ maven-toolchain/ maven-toolchain/src/ maven-toolchain/src/main/ maven-toolchain/src/main/java/ maven-toolchain/src/main/java/o

Re: checkout, edit and synergy

16 matches

Site Navigation

Mail list logo

Footer information