April 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Problem with the build?

by adrian＠jboss.org

V.Strange. I added versions to those dependencies did a clean and rebuild, then I reverted the change to the pom and now I no longer see the error? Why do we have dependencies without versions anyway in our poms, are these defined somewhere else? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041417#4041417 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041417

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: DependencyBuilder chain

by kabir.khan＠jboss.com

Can you explain the reasoning behind the chain of dependencies a bit? My knowledge pretty much stops at the AOP dependencies, which other dependencies are there? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041412#4041412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041412

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Problem with the build?

by adrian＠jboss.org

Anybody else seeing this? | Project ID: jboss:jboss-dependency | POM Location: /home/ejort/microcontainer/dependency/pom.xml | Validation Messages: | | [0] 'dependencies.dependency.version' is missing for jboss:jboss-logging-log4j | [1] 'dependencies.dependency.version' is missing for jboss:jboss-logging-spi | | | Reason: Failed to validate POM | | | [INFO] ------------------------------------------------------------------------ | [INFO] Trace | org.apache.maven.reactor.MavenExecutionException: Failed to validate POM | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) | at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278) | at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) | at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) | at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) | at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) | at org.codehaus.classworlds.Launcher.main(Launcher.java:375) | Caused by: org.apache.maven.project.InvalidProjectModelException: Failed to validate POM | at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:926) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:737) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:416) | at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:192) | at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515) | at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447) | at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:491) | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351) | ... 11 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041409#4041409 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041409

17 years, 8 months

1
0
0 / 0

[Design of Security on JBoss] - Re: SecurityAssociation no loger valid in remote client

by anil.saldhana＠jboss.com

Do you have the latest jbosssx-client.jar from security 2.0.0.snapshot? That internally has the routing for SecurityAssociation to security context concepts. So your SecurityAssociation.xxx calls internally do the security context work. We are moving away from the security association usage. In theory, you should be doing a jaas login. If there are any specific tests that you want me to take a look at, please point them here. The security context usage over the old SA is an important step towards the future security project. I do not want to hold off any WS deliverables because of this new introduction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041403#4041403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041403

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Retro CVS to SVN Migration

by pgier

"adrian(a)jboss.org" wrote : Ok. But how does Maven handle compiling on JDK5 and testing on JDK1.4? The maven surefire plugin does have an option to specify a jvm so you can run the main maven process under 1.5 but fork the tests in 1.4. It's something I'm still working on, so I don't have a detailed answer for you. But the move to SVN won't affect this. We'll still be building with ant for now ;-). For next week I just want to get the source out of the old CVS repo so that directory changes can start being tracked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041399#4041399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041399

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Maven project naming conventions

by pgier

Here are the advantages I see: 1. The repository structure will more closely match the svn structure, so it will be a little easier to determine where the jars came from based on looking at the maven repository. 2. The maven team went from a flat repository structure in maven 1 to a more deep repository structure in maven 2 (http://maven.apache.org/guides/mini/guide-relocation.html) I think their reasoning had more to do with preventing name conflicts between different organizations, but I think it would still be good to follow their conventions. 3. It is easier to do a smaller checkout of the repository with a deeper hierarchy. For example, if I want to deploy some artifact in the common project, I could just checkout the common directory without checking out the whole jboss directory. 4. The directory browsing issue also affects not just us, but also external users. We might solve the issue using something like archiva internally, but if we start syncing with the central maven repository, then external sites will have the browsing issue. In regards to the possible naming conflict issue (the reason for making the structure flat), when building it should never be an issue, because the artfiacts will always be placed into their groupId directories. But for a project like microcontainer where we want to distribute a zip with packaged jars in a lib directory, I can see it possibly being a problem if we have two projects with the same artifact ID, and they both are placed directly in the lib directory. One way we could deal with this is to include the groupId in the name of the file when we put jars into the lib directory. Another way is to put the files within their group directories within the lib directory (similar to a local repository). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041394#4041394 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041394

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Retro CVS to SVN Migration

by adrian＠jboss.org

NOTE: This is also required for jbossretrocheck. i.e. you run jbossretro on JDK5 then you check there are no missing features for your project by running the retrocheck on JDK1.4 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041382#4041382 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041382

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - Re: JBoss Retro CVS to SVN Migration

by adrian＠jboss.org

Ok. But how does Maven handle compiling on JDK5 and testing on JDK1.4? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041381#4041381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041381

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: New ClassLoader initial checkin

by adrian＠jboss.org

I've updated the holder JIRA issue with subtasks for things mentioned above: http://jira.jboss.com/jira/browse/JBOSGI-7 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041377#4041377 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041377

17 years, 8 months

1
0
0 / 0

[Design of JBoss Build System] - JBoss Retro CVS to SVN Migration

by pgier

I would like to move jboss retro from cvs to svn. The proposed new repository location is: https://svn.jboss.org/repos/jbossretro The proposed move date is Tuesday May 1st. A test conversion was done in the QA lab a few weeks ago, and the tags seem to have been converted correctly. Adrian is currently the project lead on this project, so IT would like his ok on this before doing the final conversion. The JIRA issue is here: http://jira.jboss.com/jira/browse/JBIT-1328 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041374#4041374 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041374

17 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2007