Deployment plan docs (was: Re: Conversion Tool and OpenEJB 3.0 integration status)
So a funny thing happened on the way to the theater :) On Jan 31, 2007, at 11:05 PM, David Blevins wrote: So the 10,000 foot perspective is that we are creating a conversion tool to convert the prior openejb-jar.xml into the new set of descriptors (geronimo-openejb.xml, new openejb-jar.xml, jpa entity- mappings.xml). It is expected that all existing plans will work and no one will have to or even *should* migrate just yet. We are doing this for two reasons: 1. There is significant investment in current descriptor format. These come to mind: - TCK - DayTrader - iTests - Samples - All documentation to date - All user-land apps to date It seems we ditched the openejb-jar.xml documentation anyway. I went ahead and added it into GMOxDOC20 and GMOxDOC21. I also noticed that these docs were also left: http://cwiki.apache.org/confluence/display/GMOxDOC12/geronimo-web.xml http://cwiki.apache.org/confluence/display/GMOxDOC12/geronimo-ra.xml http://cwiki.apache.org/confluence/display/GMOxDOC12/geronimo-application.xml We support backwards compatibility of our plans, so these docs should be fine for the most part. Is there some rational for not including them? -David
[jira] Resolved: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun resolved GERONIMO-3309. --- Resolution: Fixed Made more changes in rev 585796 + 585797. Added Dom4j, pull-paser, and jaxen licenses to j2g license.txt file. J2g also uses some other dependencies but they are ASL 2.0 license - Commons Logging, commons-el, jasper-5.5.15 runtime, compiler, compiler-jdt, geronimo-jsp_sepc, geronimo-servlet-spec, Removed unneeded geronimo-util and geronimo-security dependencies. For the notice.txt, I just used the ASL notice.txt proposed in the patch, as I cannot find notice file provided by Dom4j, pull-paser, or jaxen. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Lin Sun > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534966 ] Lin Sun commented on GERONIMO-3309: --- I think there are a few remaining work items need to be done for this jira (checked in some of the patch in rev 584907 - -make sure all the jars we include in the plugin jars are needed for runtime. I removed junit today as it is only used at build time. -update license and notice file. I checked in the proposed build script changes to include the license and notice files when they are in place. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Lin Sun > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun reassigned GERONIMO-3309: - Assignee: Lin Sun (was: Kevan Miller) > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Lin Sun > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
Hi Kevan, You are right, mvn install assembly:assembly would bring the target dir that contains the j2g-conversion-1.0.0-SNAPSHOT-bin.zip file which can be consumed by a user. I just did mvn install assembly:assembly and it worked fine too. I hadn't used this zip file I built from devtools tree but I used the zip file I built from sandbox before. Could you send me your full j2g build log? Thanks, Lin Kevan Miller wrote: On Oct 8, 2007, at 2:31 PM, Lin Sun wrote: Hi Kevan, Could you try building with mvn install? I am able to build j2g fine with that. Yes, 'mvn install' completes without error. However, I don't think that's running a full build... I see individual jar files are built, but there's no aggregation of jars, dependent jars, command scripts, etc. Nothing that a user can actually download... Lin, are you building and running j2g? --kevan
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
On Oct 8, 2007, at 2:31 PM, Lin Sun wrote: Hi Kevan, Could you try building with mvn install? I am able to build j2g fine with that. Yes, 'mvn install' completes without error. However, I don't think that's running a full build... I see individual jar files are built, but there's no aggregation of jars, dependent jars, command scripts, etc. Nothing that a user can actually download... Lin, are you building and running j2g? --kevan
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
Hi Kevan,
Could you try building with mvn install? I am able to build j2g fine
with that.
Thanks,
Lin
Kevan Miller wrote:
On Oct 8, 2007, at 12:53 PM, Jason Warner wrote:
It looks like you're building from the ui package. The ui package has
dependencies on a few other packages in j2g. The error your getting
is complaining about not being able to find a built version of those
packages. That error message seems to lack a description of which
package it wants that it can't find. I took a look at the pom, but
didn't really see anything regarding what packages it would want. Can
you try building j2g completely from your root j2g directory? The
same command can be used.
I'm building from j2g/trunk. The error occurs when the build reaches
org.apache.geronimo.j2g.ui.
Here's output with -e option:
[INFO]
[INFO] Building org.apache.geronimo.j2g.ui
[INFO]
[INFO] [eclipsepde:manifestbundles {execution: default}]
[INFO] [eclipsepde:install {execution: default}]
[INFO] org.eclipse.equinox.registry : 3.3.0-v20070522 already exists in
local repository.
[INFO] org.eclipse.ui.console : 3.2.0-v20070530 already exists in local
repository.
[INFO] org.eclipse.jface : 3.3.0-I20070606-0010 already exists in local
repository.
[INFO] SWTFragment: Dependency {groupId=org.eclipse.plugins,
artifactId=org.eclipse.swt.carbon.macosx, version=3.3.0-v3346, type=jar}
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] org.eclipse.swt : 3.3.0-v3346 already exists in local repository.
[INFO] org.eclipse.equinox.preferences : 3.2.100-v20070522 already
exists in local repository.
[INFO] org.eclipse.ui : 3.3.0-I20070614-0800 already exists in local
repository.
[INFO] org.eclipse.core.jobs : 3.3.0-v20070423 already exists in local
repository.
[INFO] org.eclipse.equinox.app : 1.0.0-v20070606 already exists in local
repository.
[INFO] org.eclipse.core.contenttype : 3.2.100-v20070319 already exists
in local repository.
[INFO] org.eclipse.ui.workbench : 3.3.0-I20070608-1100 already exists in
local repository.
[INFO] org.eclipse.debug.ui : 3.3.0-v20070607-1800 already exists in
local repository.
[INFO] org.eclipse.osgi : 3.3.0-v20070530 already exists in local
repository.
[INFO] org.eclipse.core.runtime : 3.3.100-v20070530 already exists in
local repository.
[INFO] org.eclipse.debug.core : 3.3.0-v20070607-1800 already exists in
local repository.
[INFO] org.eclipse.equinox.common : 3.3.0-v20070426 already exists in
local repository.
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [eclipsepde:validatemanifest {execution: validate-bundle-classpath}]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
/Users/kevan/geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.ui/target/org.apache.geronimo.j2g.ui-1.0.0-SNAPSHOT.jar
[INFO] [assembly:assembly]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Included module:
org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does not have
an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Included module:
org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does not have
an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(Ma
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
Kevan,
Strange... I also just attempted a build, and it went through
flawlessly. I did the following.
rm -rf ~/.m2/repository
svn co https://svn.apache.org/repos/asf/geronimo/devtools/j2g/trunk
j2g-build
cd j2g-build
mvn clean install
Environment is Linux - CentOS 4.5 with Sun 1.5.0_12 JDK, maven 2.0.7
Kevan Miller wrote:
On Oct 8, 2007, at 12:53 PM, Jason Warner wrote:
It looks like you're building from the ui package. The ui package
has dependencies on a few other packages in j2g. The error your
getting is complaining about not being able to find a built version
of those packages. That error message seems to lack a description of
which package it wants that it can't find. I took a look at the pom,
but didn't really see anything regarding what packages it would
want. Can you try building j2g completely from your root j2g
directory? The same command can be used.
I'm building from j2g/trunk. The error occurs when the build reaches
org.apache.geronimo.j2g.ui.
Here's output with -e option:
[INFO]
[INFO] Building org.apache.geronimo.j2g.ui
[INFO]
[INFO] [eclipsepde:manifestbundles {execution: default}]
[INFO] [eclipsepde:install {execution: default}]
[INFO] org.eclipse.equinox.registry : 3.3.0-v20070522 already exists
in local repository.
[INFO] org.eclipse.ui.console : 3.2.0-v20070530 already exists in
local repository.
[INFO] org.eclipse.jface : 3.3.0-I20070606-0010 already exists in
local repository.
[INFO] SWTFragment: Dependency {groupId=org.eclipse.plugins,
artifactId=org.eclipse.swt.carbon.macosx, version=3.3.0-v3346, type=jar}
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] org.eclipse.swt : 3.3.0-v3346 already exists in local repository.
[INFO] org.eclipse.equinox.preferences : 3.2.100-v20070522 already
exists in local repository.
[INFO] org.eclipse.ui : 3.3.0-I20070614-0800 already exists in local
repository.
[INFO] org.eclipse.core.jobs : 3.3.0-v20070423 already exists in local
repository.
[INFO] org.eclipse.equinox.app : 1.0.0-v20070606 already exists in
local repository.
[INFO] org.eclipse.core.contenttype : 3.2.100-v20070319 already exists
in local repository.
[INFO] org.eclipse.ui.workbench : 3.3.0-I20070608-1100 already exists
in local repository.
[INFO] org.eclipse.debug.ui : 3.3.0-v20070607-1800 already exists in
local repository.
[INFO] org.eclipse.osgi : 3.3.0-v20070530 already exists in local
repository.
[INFO] org.eclipse.core.runtime : 3.3.100-v20070530 already exists in
local repository.
[INFO] org.eclipse.debug.core : 3.3.0-v20070607-1800 already exists in
local repository.
[INFO] org.eclipse.equinox.common : 3.3.0-v20070426 already exists in
local repository.
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [eclipsepde:validatemanifest {execution:
validate-bundle-classpath}]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar:
/Users/kevan/geronimo/devtools/j2g/trunk/plugins/org.apache.geronimo.j2g.ui/target/org.apache.geronimo.j2g.ui-1.0.0-SNAPSHOT.jar
[INFO] [assembly:assembly]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Included module:
org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does not have
an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Included
module: org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does
not have an artifact with a file. Please ensure the package phase is
run before the assembly is generated.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:224)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycle
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
On Oct 8, 2007, at 12:53 PM, Jason Warner wrote:
It looks like you're building from the ui package. The ui package
has dependencies on a few other packages in j2g. The error your
getting is complaining about not being able to find a built version
of those packages. That error message seems to lack a description
of which package it wants that it can't find. I took a look at the
pom, but didn't really see anything regarding what packages it
would want. Can you try building j2g completely from your root j2g
directory? The same command can be used.
I'm building from j2g/trunk. The error occurs when the build reaches
org.apache.geronimo.j2g.ui.
Here's output with -e option:
[INFO]
[INFO] Building org.apache.geronimo.j2g.ui
[INFO]
[INFO] [eclipsepde:manifestbundles {execution: default}]
[INFO] [eclipsepde:install {execution: default}]
[INFO] org.eclipse.equinox.registry : 3.3.0-v20070522 already exists
in local repository.
[INFO] org.eclipse.ui.console : 3.2.0-v20070530 already exists in
local repository.
[INFO] org.eclipse.jface : 3.3.0-I20070606-0010 already exists in
local repository.
[INFO] SWTFragment: Dependency {groupId=org.eclipse.plugins,
artifactId=org.eclipse.swt.carbon.macosx, version=3.3.0-v3346, type=jar}
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] org.eclipse.swt : 3.3.0-v3346 already exists in local repository.
[INFO] org.eclipse.equinox.preferences : 3.2.100-v20070522 already
exists in local repository.
[INFO] org.eclipse.ui : 3.3.0-I20070614-0800 already exists in local
repository.
[INFO] org.eclipse.core.jobs : 3.3.0-v20070423 already exists in
local repository.
[INFO] org.eclipse.equinox.app : 1.0.0-v20070606 already exists in
local repository.
[INFO] org.eclipse.core.contenttype : 3.2.100-v20070319 already
exists in local repository.
[INFO] org.eclipse.ui.workbench : 3.3.0-I20070608-1100 already exists
in local repository.
[INFO] org.eclipse.debug.ui : 3.3.0-v20070607-1800 already exists in
local repository.
[INFO] org.eclipse.osgi : 3.3.0-v20070530 already exists in local
repository.
[INFO] org.eclipse.core.runtime : 3.3.100-v20070530 already exists in
local repository.
[INFO] org.eclipse.debug.core : 3.3.0-v20070607-1800 already exists
in local repository.
[INFO] org.eclipse.equinox.common : 3.3.0-v20070426 already exists in
local repository.
[INFO] org.eclipse.swt.carbon.macosx : 3.3.0-v3346 already exists in
local repository.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [eclipsepde:validatemanifest {execution: validate-bundle-
classpath}]
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] No tests to run.
[INFO] [jar:jar]
[INFO] Building jar: /Users/kevan/geronimo/devtools/j2g/trunk/plugins/
org.apache.geronimo.j2g.ui/target/org.apache.geronimo.j2g.ui-1.0.0-
SNAPSHOT.jar
[INFO] [assembly:assembly]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Included module: org.apache.geronimo.tools:j2g-plugins:pom:
1.0.0-SNAPSHOT does not have an artifact with a file. Please ensure
the package phase is run before the assembly is generated.
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Included
module: org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does
not have an artifact with a file. Please ensure the package phase is
run before the assembly is generated.
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(DefaultLifecycleExecutor.java:493)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal
(DefaultLifecycleExecutor.java:463)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:224)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.ref
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
It looks like you're building from the ui package. The ui package has dependencies on a few other packages in j2g. The error your getting is complaining about not being able to find a built version of those packages. That error message seems to lack a description of which package it wants that it can't find. I took a look at the pom, but didn't really see anything regarding what packages it would want. Can you try building j2g completely from your root j2g directory? The same command can be used. On 10/8/07, Kevan Miller <[EMAIL PROTECTED]> wrote: > > > On Oct 8, 2007, at 11:29 AM, Jason Warner wrote: > > > > > You're using the correct command to build the tool. I just checked > > out the latest version and built it with no issues? It was > > recently moved to the devtools component. Is that where you > > checked it out from? What problems are you having? > > mvn install assembly:assembly > ... > [INFO] Building jar: /Users/kevan/geronimo/devtools/j2g/trunk/plugins/ > org.apache.geronimo.j2g.ui/target/org.apache.geronimo.j2g.ui-1.0.0- > SNAPSHOT.jar > [INFO] [assembly:assembly] > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Included module: org.apache.geronimo.tools:j2g-plugins:pom: > 1.0.0-SNAPSHOT does not have an artifact with a file. Please ensure > the package phase is run before the assembly is generated. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 1 minute 58 seconds > [INFO] Finished at: Mon Oct 08 10:42:01 EDT 2007 > [INFO] Final Memory: 30M/85M > [INFO] > > > --kevan > > >
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
On Oct 8, 2007, at 11:29 AM, Jason Warner wrote: You're using the correct command to build the tool. I just checked out the latest version and built it with no issues? It was recently moved to the devtools component. Is that where you checked it out from? What problems are you having? mvn install assembly:assembly ... [INFO] Building jar: /Users/kevan/geronimo/devtools/j2g/trunk/plugins/ org.apache.geronimo.j2g.ui/target/org.apache.geronimo.j2g.ui-1.0.0- SNAPSHOT.jar [INFO] [assembly:assembly] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Included module: org.apache.geronimo.tools:j2g-plugins:pom: 1.0.0-SNAPSHOT does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 58 seconds [INFO] Finished at: Mon Oct 08 10:42:01 EDT 2007 [INFO] Final Memory: 30M/85M [INFO] --kevan
Re: [jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
You're using the correct command to build the tool. I just checked out the latest version and built it with no issues? It was recently moved to the devtools component. Is that where you checked it out from? What problems are you having? On 10/8/07, Kevan Miller (JIRA) <[EMAIL PROTECTED]> wrote: > > > [ > https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533139] > > Kevan Miller commented on GERONIMO-3309: > > > Hi Jason, > Apologies. > > Although you mention a number of licenses in a previous comment, I don't > see these licenses in either of your patch files. > > I'm not currently able to build j2g (mvn install assembly:assembly). How > should I be building? > > > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > > --- > > > > Key: GERONIMO-3309 > > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > > Project: Geronimo > > Issue Type: Improvement > > Security Level: public(Regular issues) > > Components: J2G > >Reporter: Jason Warner > >Assignee: Kevan Miller > > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533139 ] Kevan Miller commented on GERONIMO-3309: Hi Jason, Apologies. Although you mention a number of licenses in a previous comment, I don't see these licenses in either of your patch files. I'm not currently able to build j2g (mvn install assembly:assembly). How should I be building? > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531518 ] Jason Warner commented on GERONIMO-3309: Kevan, I'd like to close out all the old J2G issues that have carried over from sandbox, if possible. Have you taken a look at the files to verfiy whether they are correct or not? > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3309: --- Assignee: Kevan Miller (was: Jason Warner) > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner closed GERONIMO-3347. -- Resolution: Fixed > Improve output formatting in J2G Conversion tool > > > Key: GERONIMO-3347 > URL: https://issues.apache.org/jira/browse/GERONIMO-3347 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3347.patch > > > The current output for any of the subtools for the J2G Conversion Tool is > sometimes vague and confusing. The formatting could also be improved to make > it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3347: --- Attachment: Geronimo-3347.patch This new patch was required due to commit of Geronimo-3342. > Improve output formatting in J2G Conversion tool > > > Key: GERONIMO-3347 > URL: https://issues.apache.org/jira/browse/GERONIMO-3347 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3347.patch > > > The current output for any of the subtools for the J2G Conversion Tool is > sometimes vague and confusing. The formatting could also be improved to make > it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3347: --- Attachment: (was: Geronimo-3347.patch) > Improve output formatting in J2G Conversion tool > > > Key: GERONIMO-3347 > URL: https://issues.apache.org/jira/browse/GERONIMO-3347 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3347.patch > > > The current output for any of the subtools for the J2G Conversion Tool is > sometimes vague and confusing. The formatting could also be improved to make > it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3347: --- Patch Info: [Patch Available] > Improve output formatting in J2G Conversion tool > > > Key: GERONIMO-3347 > URL: https://issues.apache.org/jira/browse/GERONIMO-3347 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3347.patch > > > The current output for any of the subtools for the J2G Conversion Tool is > sometimes vague and confusing. The formatting could also be improved to make > it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3347: --- Attachment: Geronimo-3347.patch Fixed spelling and grammar errors so that output makes more sense. Modified formatting for output statements. > Improve output formatting in J2G Conversion tool > > > Key: GERONIMO-3347 > URL: https://issues.apache.org/jira/browse/GERONIMO-3347 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3347.patch > > > The current output for any of the subtools for the J2G Conversion Tool is > sometimes vague and confusing. The formatting could also be improved to make > it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3347) Improve output formatting in J2G Conversion tool
Improve output formatting in J2G Conversion tool Key: GERONIMO-3347 URL: https://issues.apache.org/jira/browse/GERONIMO-3347 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: J2G Reporter: Jason Warner Assignee: Jason Warner The current output for any of the subtools for the J2G Conversion Tool is sometimes vague and confusing. The formatting could also be improved to make it easier to read. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3309: --- Attachment: Geronimo-3309Update.patch This patch should contain all the necessary updates to the LICENSE.txt and NOTICE.txt files. Each jar within the deployable now contains an appropriate LICENSE.txt and NOTICE.txt file in their respective META-INF directory. I think that I've included all the appropriate licenses and such but I would very much appreciate someone with more license experience taking a look at this. There are a few non-standard licenses that needed to be included that looked ok to me but I could be wrong. I only know enough legalese to ask where the bathroom is. List of non-Apache product licenses included in this tool: BouncyCastle (As part of geronimo-util) - http://bouncycastle.org/license.html DOM4J - http://www.dom4j.org/license.html Jaxen - http://jaxen.org/license.html Junit - Uses CPL 1.0 XML Pull Parser - http://www.extreme.indiana.edu/xgws/xsoap/xpp/download/PullParser2/LICENSE.txt > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3309.patch, Geronimo-3309Update.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reassigned GERONIMO-3309: -- Assignee: Jason Warner (was: Kevan Miller) > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514690 ] Kevan Miller commented on GERONIMO-3309: Cool. I'm going to assign back to you then. Will hold off applying the patch, also. Let's get everything right, first... FYI, here's the error i get from 'mvn clean install assembly:assembly' [INFO] [assembly:assembly] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Included module: org.apache.geronimo.tools:j2g-plugins:pom:1.0.0-SNAPSHOT does not have an artifact with a file. Please ensure the package phase is run before the assembly is generated. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514623 ] Jason Warner commented on GERONIMO-3309: I'll definitely take a look into this, Kevan. In regards to J2G not building completely for you, what command did you use to build? It should be built using "mvn install assembly:assembly" if you want the deployable to be built as well. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514522 ] Kevan Miller commented on GERONIMO-3309: J2G is not building completely for me, at the moment. I can build enough to see that there's additional licensing work required. For instance, there are a number of jar files being included in j2g jar files. For instance, org.apache.geronimo.j2g.util-1.0.0-SNAPSHOT.jar includes pull-parser-2.1.10.jar. We need to know the license(s) that apply to this jar file. pull-parser comes out of Extreme Labs, it looks like. It's not clear to me what license(s) apply to this jar. We need to pin this down precisely. This process needs to occur for all such dependencies. As apropriate, these licenses need to be reflected in the J2G license and notice files. I also noted that the J2G jar files are missing license and notice files. They must have them. These files should reflect the license and notice information for each jar file. For general guidance on apache license and notice file handling, see -- http://www.apache.org/legal/src-headers.html For guidance on what licenses are acceptable to Apache, see -- http://people.apache.org/~cliffs/3party.html Jason, if you're interested in doing this investigation, that would be great. However, a Geronimo committer is going to need to carefully review all of this... > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514259 ] Kevan Miller commented on GERONIMO-3309: Looks good. I'd update the following in the NOTICE file: informally known as the "IBM Console CLA" That pertains to a previous software grant for the admin console. I see no reason to mention an informal name for the CCLA. I'll change that. I haven't tested a build, yet. Once I do, I'll commit. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reassigned GERONIMO-3309: -- Assignee: Kevan Miller (was: Jason Warner) > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Kevan Miller > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3309: --- Patch Info: [Patch Available] > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3309: --- Attachment: Geronimo-3309.patch The LICENSE.txt file is just a straight copy and paste job. I had to fill in some details for the orginal code donation in NOTICE.txt, though. If someone could peek at that and make sure the wording and such is alright, I'd appreciate it. The JIRA for the original code donation is here https://issues.apache.org/jira/browse/GERONIMO-2743. > Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool > --- > > Key: GERONIMO-3309 > URL: https://issues.apache.org/jira/browse/GERONIMO-3309 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3309.patch > > > The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3309) Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool
Add missing LICENSE.txt and NOTICE.txt files to the J2G conversion tool --- Key: GERONIMO-3309 URL: https://issues.apache.org/jira/browse/GERONIMO-3309 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: J2G Reporter: Jason Warner Assignee: Jason Warner The J2G conversion tool is missing the LICENSE.txt and NOTICE.txt files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: J2G Conversion tool got a makeover. Now what?
is launched using a series of scripts, so perhaps a button > that can launch these scripts would be feasible. Anyone know of a > better way? > > Jason Warner > > > On 6/14/07, Paul McMahan < [EMAIL PROTECTED]> wrote: Fantastic > work, thanks for your contributions! > > After all this testing and improvement we could consider moving J2G > from sandbox to a more stable location where it can be properly > released and maintained. If our dev community expresses interest in > doing that then maybe the devtools subproject is a good place for > it. Asking for feedback on the users list would help us know how to > proceed as well. > > Thinking from the user's perspective, I wonder if J2G can be > integrated with our eclipse plugin somehow? For example could our > eclipse plugin wrapper the J2G functionality in a wizard, button, or > context menu item? Perhaps something simple for starters, just some > way launch the tool from inside the IDE. Since J2G is itself > implemented as an eclipse plugin it would seem strange to provide no > UI controls for it or integration point with our current eclipse > plugin. > > > Best wishes, > Paul > > On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: > > > Some of you may have noticed the recent activity on the devlist in > > regards to the J2G conversion tool. Erik Craig and I have been > > making significant improvements in the functionality and usability > > of this tool. Some of these changes include adding new > > documentation on the wiki, fixing scripts to provide more > > functionality, ensuring unix functionality, and general debugging > > for both the code and the unit tests. Now that these changes have > > been made, it might be appropriate to have another look at the tool > > and see if it is ready to be moved out of sandbox and into > > devtools. Any and all comments are welcome. > > > > For those interested, here's a link to the documentation http:// > > cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html > >
Re: J2G Conversion tool got a makeover. Now what?
On Jun 27, 2007, at 12:22 PM, Erik B. Craig wrote: The other (perhaps simpler) idea for a UI integration I came up with doesn't necessarily involve any WTP pieces, as it would be to simply have a window or menu available that would have buttons/ options to run the three components and show the output from them. That's sorta what I had in mind too for the short term. Longer term I agree with Sachin that full scale integration via WTP would be cool. Best wishes, Paul
Re: J2G Conversion tool got a makeover. Now what?
Sachin, I've been digging into documentation on WTP and Eclipse plug-ins in general over the last few days, and I am wondering what specifically you have in mind with this approach. Based on what you have said, the best solution I've been able to think of is perhaps adding an additional 'target runtime' to be selected from the list that would be called something like 'j2g migration', at which point the user would be prompted for a path to an existing geronimo server, and after clicking 'next', it would (correct me if it can even DO this) execute the 1st piece of j2g in a terminal (or maybe behind the scenes?), displaying the output, a next again would do the same for the second piece, a third next would do the same for the final piece. Other than this, which I'm not entirely sure of the feasibility of it at this point, I don't know that trying to have it auto detect a changeover or something would necessarily work, because of the fact that you can have multiple target runtimes selected. The other (perhaps simpler) idea for a UI integration I came up with doesn't necessarily involve any WTP pieces, as it would be to simply have a window or menu available that would have buttons/options to run the three components and show the output from them. What are your thoughts? Thanks -Erik On 6/15/07, Sachin Patel <[EMAIL PROTECTED]> wrote: At this time as its currently implemented, I don't think it would make a good inside the UI. The context you're working in the IDE is a "project" under development and J2G currently doesn't operate under this context. There would be no real advantage to allow it to be invoked in the UI since it can't be operated on projects in the workspace. If any integration into the UI then the proper approach and it would be fairly trivial is to go ahead with WTP integration... All J2EE projects in WTP have a notion of a target runtime. Every application is required to have its target runtime set (JBoss, WebSphere, Geronimo, etc..). At any point in time you can retarget an applications runtime to a different one. So if an application's runtime is set to JBoss, you can currently swap it over to Geronimo. This operation can be extended to perform any other tasks. In our case, we would simply process the projects and traverse through the content running any migrations necessary. I don't think this would be too hard to do. Its just picking out the core peices currently inside J2G that actually do the migration on particular resources and wrapping those in 1 or more WTP operations. If this approach was taken I would be +1 to integrating this within the Eclipse Plugin. hope that helps. -sachin On Jun 14, 2007, at 5:54 PM, Jason Warner wrote: > Paul, > > Thanks for the feedback! > > In regards to integration with the eclipse plugin, I don't believe > that would be an easy task to accomplish. From my understanding, > the eclipse-plugin runs on top of WTP whereas the J2G tool is a > headless plugin. I believe the J2G tool would need to be rewritten > using WTP to allow for integration. > > As for a button or other GUI way of launching the tool, I think > that's a great idea. I'm still rather new to working with eclipse > plugins, though, so I'm not quite sure how that could be done. The > tool is launched using a series of scripts, so perhaps a button > that can launch these scripts would be feasible. Anyone know of a > better way? > > Jason Warner > > > On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic > work, thanks for your contributions! > > After all this testing and improvement we could consider moving J2G > from sandbox to a more stable location where it can be properly > released and maintained. If our dev community expresses interest in > doing that then maybe the devtools subproject is a good place for > it. Asking for feedback on the users list would help us know how to > proceed as well. > > Thinking from the user's perspective, I wonder if J2G can be > integrated with our eclipse plugin somehow? For example could our > eclipse plugin wrapper the J2G functionality in a wizard, button, or > context menu item? Perhaps something simple for starters, just some > way launch the tool from inside the IDE. Since J2G is itself > implemented as an eclipse plugin it would seem strange to provide no > UI controls for it or integration point with our current eclipse > plugin. > > > Best wishes, > Paul > > On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: > > > Some of you may have noticed the recent activity on the devlist in > > regards to the J2G conversion tool. Erik Craig and I have been > > making significant improvements in the functionality and usability >
Re: J2G Conversion tool got a makeover. Now what?
Thanks for the reply, Sachin. I understand what you're saying about there being no advantage to adding it to the UI. I think if it were implemented the way you had mentioned, there would still be some merit, though. It'd be great if we could get some other members of the community to weigh in, though. Anybody else have any thoughts? Thanks, Jason Warner On 6/15/07, Sachin Patel <[EMAIL PROTECTED]> wrote: At this time as its currently implemented, I don't think it would make a good inside the UI. The context you're working in the IDE is a "project" under development and J2G currently doesn't operate under this context. There would be no real advantage to allow it to be invoked in the UI since it can't be operated on projects in the workspace. If any integration into the UI then the proper approach and it would be fairly trivial is to go ahead with WTP integration... All J2EE projects in WTP have a notion of a target runtime. Every application is required to have its target runtime set (JBoss, WebSphere, Geronimo, etc..). At any point in time you can retarget an applications runtime to a different one. So if an application's runtime is set to JBoss, you can currently swap it over to Geronimo. This operation can be extended to perform any other tasks. In our case, we would simply process the projects and traverse through the content running any migrations necessary. I don't think this would be too hard to do. Its just picking out the core peices currently inside J2G that actually do the migration on particular resources and wrapping those in 1 or more WTP operations. If this approach was taken I would be +1 to integrating this within the Eclipse Plugin. hope that helps. -sachin On Jun 14, 2007, at 5:54 PM, Jason Warner wrote: > Paul, > > Thanks for the feedback! > > In regards to integration with the eclipse plugin, I don't believe > that would be an easy task to accomplish. From my understanding, > the eclipse-plugin runs on top of WTP whereas the J2G tool is a > headless plugin. I believe the J2G tool would need to be rewritten > using WTP to allow for integration. > > As for a button or other GUI way of launching the tool, I think > that's a great idea. I'm still rather new to working with eclipse > plugins, though, so I'm not quite sure how that could be done. The > tool is launched using a series of scripts, so perhaps a button > that can launch these scripts would be feasible. Anyone know of a > better way? > > Jason Warner > > > On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic > work, thanks for your contributions! > > After all this testing and improvement we could consider moving J2G > from sandbox to a more stable location where it can be properly > released and maintained. If our dev community expresses interest in > doing that then maybe the devtools subproject is a good place for > it. Asking for feedback on the users list would help us know how to > proceed as well. > > Thinking from the user's perspective, I wonder if J2G can be > integrated with our eclipse plugin somehow? For example could our > eclipse plugin wrapper the J2G functionality in a wizard, button, or > context menu item? Perhaps something simple for starters, just some > way launch the tool from inside the IDE. Since J2G is itself > implemented as an eclipse plugin it would seem strange to provide no > UI controls for it or integration point with our current eclipse > plugin. > > > Best wishes, > Paul > > On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: > > > Some of you may have noticed the recent activity on the devlist in > > regards to the J2G conversion tool. Erik Craig and I have been > > making significant improvements in the functionality and usability > > of this tool. Some of these changes include adding new > > documentation on the wiki, fixing scripts to provide more > > functionality, ensuring unix functionality, and general debugging > > for both the code and the unit tests. Now that these changes have > > been made, it might be appropriate to have another look at the tool > > and see if it is ready to be moved out of sandbox and into > > devtools. Any and all comments are welcome. > > > > For those interested, here's a link to the documentation http:// > > cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html > >
Re: J2G Conversion tool got a makeover. Now what?
At this time as its currently implemented, I don't think it would make a good inside the UI. The context you're working in the IDE is a "project" under development and J2G currently doesn't operate under this context. There would be no real advantage to allow it to be invoked in the UI since it can't be operated on projects in the workspace. If any integration into the UI then the proper approach and it would be fairly trivial is to go ahead with WTP integration... All J2EE projects in WTP have a notion of a target runtime. Every application is required to have its target runtime set (JBoss, WebSphere, Geronimo, etc..). At any point in time you can retarget an applications runtime to a different one. So if an application's runtime is set to JBoss, you can currently swap it over to Geronimo. This operation can be extended to perform any other tasks. In our case, we would simply process the projects and traverse through the content running any migrations necessary. I don't think this would be too hard to do. Its just picking out the core peices currently inside J2G that actually do the migration on particular resources and wrapping those in 1 or more WTP operations. If this approach was taken I would be +1 to integrating this within the Eclipse Plugin. hope that helps. -sachin On Jun 14, 2007, at 5:54 PM, Jason Warner wrote: Paul, Thanks for the feedback! In regards to integration with the eclipse plugin, I don't believe that would be an easy task to accomplish. From my understanding, the eclipse-plugin runs on top of WTP whereas the J2G tool is a headless plugin. I believe the J2G tool would need to be rewritten using WTP to allow for integration. As for a button or other GUI way of launching the tool, I think that's a great idea. I'm still rather new to working with eclipse plugins, though, so I'm not quite sure how that could be done. The tool is launched using a series of scripts, so perhaps a button that can launch these scripts would be feasible. Anyone know of a better way? Jason Warner On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic work, thanks for your contributions! After all this testing and improvement we could consider moving J2G from sandbox to a more stable location where it can be properly released and maintained. If our dev community expresses interest in doing that then maybe the devtools subproject is a good place for it. Asking for feedback on the users list would help us know how to proceed as well. Thinking from the user's perspective, I wonder if J2G can be integrated with our eclipse plugin somehow? For example could our eclipse plugin wrapper the J2G functionality in a wizard, button, or context menu item? Perhaps something simple for starters, just some way launch the tool from inside the IDE. Since J2G is itself implemented as an eclipse plugin it would seem strange to provide no UI controls for it or integration point with our current eclipse plugin. Best wishes, Paul On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: > Some of you may have noticed the recent activity on the devlist in > regards to the J2G conversion tool. Erik Craig and I have been > making significant improvements in the functionality and usability > of this tool. Some of these changes include adding new > documentation on the wiki, fixing scripts to provide more > functionality, ensuring unix functionality, and general debugging > for both the code and the unit tests. Now that these changes have > been made, it might be appropriate to have another look at the tool > and see if it is ready to be moved out of sandbox and into > devtools. Any and all comments are welcome. > > For those interested, here's a link to the documentation http:// > cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html
Re: J2G Conversion tool got a makeover. Now what?
Paul, Thanks for the feedback! In regards to integration with the eclipse plugin, I don't believe that would be an easy task to accomplish. From my understanding, the eclipse-plugin runs on top of WTP whereas the J2G tool is a headless plugin. I believe the J2G tool would need to be rewritten using WTP to allow for integration. As for a button or other GUI way of launching the tool, I think that's a great idea. I'm still rather new to working with eclipse plugins, though, so I'm not quite sure how that could be done. The tool is launched using a series of scripts, so perhaps a button that can launch these scripts would be feasible. Anyone know of a better way? Jason Warner On 6/14/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Fantastic work, thanks for your contributions! After all this testing and improvement we could consider moving J2G from sandbox to a more stable location where it can be properly released and maintained. If our dev community expresses interest in doing that then maybe the devtools subproject is a good place for it. Asking for feedback on the users list would help us know how to proceed as well. Thinking from the user's perspective, I wonder if J2G can be integrated with our eclipse plugin somehow? For example could our eclipse plugin wrapper the J2G functionality in a wizard, button, or context menu item? Perhaps something simple for starters, just some way launch the tool from inside the IDE. Since J2G is itself implemented as an eclipse plugin it would seem strange to provide no UI controls for it or integration point with our current eclipse plugin. Best wishes, Paul On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: > Some of you may have noticed the recent activity on the devlist in > regards to the J2G conversion tool. Erik Craig and I have been > making significant improvements in the functionality and usability > of this tool. Some of these changes include adding new > documentation on the wiki, fixing scripts to provide more > functionality, ensuring unix functionality, and general debugging > for both the code and the unit tests. Now that these changes have > been made, it might be appropriate to have another look at the tool > and see if it is ready to be moved out of sandbox and into > devtools. Any and all comments are welcome. > > For those interested, here's a link to the documentation http:// > cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html
Re: J2G Conversion tool got a makeover. Now what?
Fantastic work, thanks for your contributions! After all this testing and improvement we could consider moving J2G from sandbox to a more stable location where it can be properly released and maintained. If our dev community expresses interest in doing that then maybe the devtools subproject is a good place for it. Asking for feedback on the users list would help us know how to proceed as well. Thinking from the user's perspective, I wonder if J2G can be integrated with our eclipse plugin somehow? For example could our eclipse plugin wrapper the J2G functionality in a wizard, button, or context menu item? Perhaps something simple for starters, just some way launch the tool from inside the IDE. Since J2G is itself implemented as an eclipse plugin it would seem strange to provide no UI controls for it or integration point with our current eclipse plugin. Best wishes, Paul On Jun 14, 2007, at 2:26 PM, Jason Warner wrote: Some of you may have noticed the recent activity on the devlist in regards to the J2G conversion tool. Erik Craig and I have been making significant improvements in the functionality and usability of this tool. Some of these changes include adding new documentation on the wiki, fixing scripts to provide more functionality, ensuring unix functionality, and general debugging for both the code and the unit tests. Now that these changes have been made, it might be appropriate to have another look at the tool and see if it is ready to be moved out of sandbox and into devtools. Any and all comments are welcome. For those interested, here's a link to the documentation http:// cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html
J2G Conversion tool got a makeover. Now what?
Some of you may have noticed the recent activity on the devlist in regards to the J2G conversion tool. Erik Craig and I have been making significant improvements in the functionality and usability of this tool. Some of these changes include adding new documentation on the wiki, fixing scripts to provide more functionality, ensuring unix functionality, and general debugging for both the code and the unit tests. Now that these changes have been made, it might be appropriate to have another look at the tool and see if it is ready to be moved out of sandbox and into devtools. Any and all comments are welcome. For those interested, here's a link to the documentation http://cwiki.apache.org/GMOxDOC11/j2g-migration-tool.html
[jira] Resolved: (GERONIMO-3217) J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file instead of overwriting.
[ https://issues.apache.org/jira/browse/GERONIMO-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods resolved GERONIMO-3217. Resolution: Fixed Committed revision 544932 in sandbox. > J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file > instead of overwriting. > - > > Key: GERONIMO-3217 > URL: https://issues.apache.org/jira/browse/GERONIMO-3217 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3217.patch > > > An openejb-jar.xml file is created from the exisiting JBoss xml files when > the descriptor tool is run. This openejb-jar.xml should be deleted and > remade each time the descriptor tool is run. As it is now, the tool appends > the new xml data into existing elements resulting in an xml that is invalid > due to duplicate entries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3217) J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file instead of overwriting.
[ https://issues.apache.org/jira/browse/GERONIMO-3217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Warner updated GERONIMO-3217: --- Attachment: Geronimo-3217.patch CMPDescriptorTool.java has been changed to check for an existing openejb-jar.xml. If it finds an existing file, it is deleted to avoid the issue. > J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file > instead of overwriting. > - > > Key: GERONIMO-3217 > URL: https://issues.apache.org/jira/browse/GERONIMO-3217 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: J2G >Reporter: Jason Warner >Assignee: Jason Warner > Attachments: Geronimo-3217.patch > > > An openejb-jar.xml file is created from the exisiting JBoss xml files when > the descriptor tool is run. This openejb-jar.xml should be deleted and > remade each time the descriptor tool is run. As it is now, the tool appends > the new xml data into existing elements resulting in an xml that is invalid > due to duplicate entries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3217) J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file instead of overwriting.
J2G Conversion Tool: Descriptors subtool appends to the openejb-jar.xml file instead of overwriting. - Key: GERONIMO-3217 URL: https://issues.apache.org/jira/browse/GERONIMO-3217 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: J2G Reporter: Jason Warner Assignee: Jason Warner An openejb-jar.xml file is created from the exisiting JBoss xml files when the descriptor tool is run. This openejb-jar.xml should be deleted and remade each time the descriptor tool is run. As it is now, the tool appends the new xml data into existing elements resulting in an xml that is invalid due to duplicate entries. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2743. -- Resolution: Fixed Thanks for the updated attachment. I ended up just removing the "IBM Confidential" line from the COPYRIGHT.txt instead of deleting the file, which I think was fine to do now that you have provided an additional attachment that does not contain the file at all. > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik > Assigned To: Paul McMahan >Priority: Minor > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, > J2G-Migration_2.0.0_src_20070302-1501.zip, > J2G-Migration_2.0.0_src_20070321-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] J2G Conversion tool acceptance
Thanks Jeffrey! Best wishes, Paul On 3/21/07, Jeffrey Faelnar <[EMAIL PROTECTED]> wrote: Paul, I updated the bundle, removing the COPYRIGHT.txt file, and reattached the zip to JIRA. Thanks. On 3/21/07, Paul McMahan < [EMAIL PROTECTED]> wrote: > Jeffery, after filing the IP clearance form I checked J2G into the > sandbox. At the time I was thinking it would be OK to include this > file > https://svn.apache.org/repos/asf/geronimo/sandbox/j2g/COPYRIGHT.txt > But then later someone pointed out that this file could potentially be > an issue. Could you do us a favor and reattach the zip to the JIRA > with that COPYRIGHT.txt file removed? > > Best wishes, > Paul > > On 2/8/07, Jeffrey Faelnar <[EMAIL PROTECTED]> wrote: > > Hi Paul, > > > > We're in the process of getting the codebase cleaned up, refactored, and > > adding maven support. However, I will need your assistance with the > > ip-clearance form. Thanks. > > > > -Jeff > > > > > > On 2/8/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > > > IIUC we're at step 3 of this process right now -- contributor replaces > > > copyright statements with the standard apache header. Adding maven > > > support and changing the package names from com.ibm.* to org.apache.* > > > would be very useful as well if that's possible. I can help with > > > step 4 - submitting the ip clearance form and checking in to > > > geronimo/sandbox. Once in sandbox we should discuss how/when it can > > > be updated to support geronimo 1.2 & 2.0 and merged with the devtools > > > subproject. > > > > > > Best wishes, > > > Paul > > > > > > On 2/1/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > > > > Here's the process : > > > > > > > > 1) Contributor offers code > > > > > > > > 2) Project decides to accept or reject code. Formally, this is the > > > > PMC, but everyone should chime in. > > > > > > > > 3) Contributor provides CCLA, cleans up code to remove copyright > > > > statements, and puts the standard apache file header in place. > > > > > > > > 4) Project accepts code contribution and registers the code > > > > contribution w/ the incubator with an ip_clearance form : > > > > > > > > > > http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ > > > > ip-clearance/ > > > > > > > > 5) Happy users convert their JBoss apps to Geronimo. > > > > > > > > There's no need for the creation of a podling for accepting code into > > > > an existing project, unless you wanted to bring in people and create > > > > a community around it. We simply need to file an ip-clearance form > > > > w/ the incubator that notes that we did the due diligence in > > > > accepting the code. > > > > > > > > geir > > > > > > > > > > > > > > > > On Jan 31, 2007, at 10:10 AM, Filip Hanik - Dev Lists wrote: > > > > > > > > > This is the formal vote to accept the J2G codebase and bring it > > > > > through incubation (see > > http://marc.theaimsgroup.com/?l=geronimo- > > > > > dev&m=116906208022256&w=2) > > > > > The final destination is to be part of the geronimo devtool > > > > > subproject. > > > > > (see http://marc.theaimsgroup.com/?l=geronimo- > > > > > dev&m=116958894929809&w=2) > > > > > > > > > > The code donation is located at: > > > > > https://issues.apache.org/jira/browse/GERONIMO-2743 > > > > > > > > > > [ ] +1 lets bring it in, this is great > > > > > [ ] 0 do what ever you want, not my cup of tea > > > > > [ ] -1 keep it out of our sight, I have a good reason > > > > > > > > > > Optional > > > > > [ ] I'm willing to mentor this project while it is in incubation > > > > > [ ] I'm willing to champion the effort while it is in incubation > > > > > > > > > > Committers' votes are binding, all other votes will be duly noted > > > > > > > > > > Best regards > > > > > Filip > > > > > > > > > > > > > > > >
Re: [VOTE] J2G Conversion tool acceptance
Paul, I updated the bundle, removing the COPYRIGHT.txt file, and reattached the zip to JIRA. Thanks. On 3/21/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Jeffery, after filing the IP clearance form I checked J2G into the sandbox. At the time I was thinking it would be OK to include this file https://svn.apache.org/repos/asf/geronimo/sandbox/j2g/COPYRIGHT.txt But then later someone pointed out that this file could potentially be an issue. Could you do us a favor and reattach the zip to the JIRA with that COPYRIGHT.txt file removed? Best wishes, Paul On 2/8/07, Jeffrey Faelnar <[EMAIL PROTECTED]> wrote: > Hi Paul, > > We're in the process of getting the codebase cleaned up, refactored, and > adding maven support. However, I will need your assistance with the > ip-clearance form. Thanks. > > -Jeff > > > On 2/8/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > > IIUC we're at step 3 of this process right now -- contributor replaces > > copyright statements with the standard apache header. Adding maven > > support and changing the package names from com.ibm.* to org.apache.* > > would be very useful as well if that's possible. I can help with > > step 4 - submitting the ip clearance form and checking in to > > geronimo/sandbox. Once in sandbox we should discuss how/when it can > > be updated to support geronimo 1.2 & 2.0 and merged with the devtools > > subproject. > > > > Best wishes, > > Paul > > > > On 2/1/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > > > Here's the process : > > > > > > 1) Contributor offers code > > > > > > 2) Project decides to accept or reject code. Formally, this is the > > > PMC, but everyone should chime in. > > > > > > 3) Contributor provides CCLA, cleans up code to remove copyright > > > statements, and puts the standard apache file header in place. > > > > > > 4) Project accepts code contribution and registers the code > > > contribution w/ the incubator with an ip_clearance form : > > > > > > > http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ > > > ip-clearance/ > > > > > > 5) Happy users convert their JBoss apps to Geronimo. > > > > > > There's no need for the creation of a podling for accepting code into > > > an existing project, unless you wanted to bring in people and create > > > a community around it. We simply need to file an ip-clearance form > > > w/ the incubator that notes that we did the due diligence in > > > accepting the code. > > > > > > geir > > > > > > > > > > > > On Jan 31, 2007, at 10:10 AM, Filip Hanik - Dev Lists wrote: > > > > > > > This is the formal vote to accept the J2G codebase and bring it > > > > through incubation (see > http://marc.theaimsgroup.com/?l=geronimo- > > > > dev&m=116906208022256&w=2) > > > > The final destination is to be part of the geronimo devtool > > > > subproject. > > > > (see http://marc.theaimsgroup.com/?l=geronimo- > > > > dev&m=116958894929809&w=2) > > > > > > > > The code donation is located at: > > > > https://issues.apache.org/jira/browse/GERONIMO-2743 > > > > > > > > [ ] +1 lets bring it in, this is great > > > > [ ] 0 do what ever you want, not my cup of tea > > > > [ ] -1 keep it out of our sight, I have a good reason > > > > > > > > Optional > > > > [ ] I'm willing to mentor this project while it is in incubation > > > > [ ] I'm willing to champion the effort while it is in incubation > > > > > > > > Committers' votes are binding, all other votes will be duly noted > > > > > > > > Best regards > > > > Filip > > > > > > > > > >
[jira] Updated: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2743: -- Attachment: J2G-Migration_2.0.0_src_20070321-1501.zip COPYRIGHT.txt file removed. > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik > Assigned To: Paul McMahan >Priority: Minor > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, > J2G-Migration_2.0.0_src_20070302-1501.zip, > J2G-Migration_2.0.0_src_20070321-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan reopened GERONIMO-2743: reopening the issue so the contributor can attach a zip with the COPYRIGHT.txt removed > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik > Assigned To: Paul McMahan >Priority: Minor > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, > J2G-Migration_2.0.0_src_20070302-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] J2G Conversion tool acceptance
Jeffery, after filing the IP clearance form I checked J2G into the sandbox. At the time I was thinking it would be OK to include this file https://svn.apache.org/repos/asf/geronimo/sandbox/j2g/COPYRIGHT.txt But then later someone pointed out that this file could potentially be an issue. Could you do us a favor and reattach the zip to the JIRA with that COPYRIGHT.txt file removed? Best wishes, Paul On 2/8/07, Jeffrey Faelnar <[EMAIL PROTECTED]> wrote: Hi Paul, We're in the process of getting the codebase cleaned up, refactored, and adding maven support. However, I will need your assistance with the ip-clearance form. Thanks. -Jeff On 2/8/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > IIUC we're at step 3 of this process right now -- contributor replaces > copyright statements with the standard apache header. Adding maven > support and changing the package names from com.ibm.* to org.apache.* > would be very useful as well if that's possible. I can help with > step 4 - submitting the ip clearance form and checking in to > geronimo/sandbox. Once in sandbox we should discuss how/when it can > be updated to support geronimo 1.2 & 2.0 and merged with the devtools > subproject. > > Best wishes, > Paul > > On 2/1/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > > Here's the process : > > > > 1) Contributor offers code > > > > 2) Project decides to accept or reject code. Formally, this is the > > PMC, but everyone should chime in. > > > > 3) Contributor provides CCLA, cleans up code to remove copyright > > statements, and puts the standard apache file header in place. > > > > 4) Project accepts code contribution and registers the code > > contribution w/ the incubator with an ip_clearance form : > > > > http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ > > ip-clearance/ > > > > 5) Happy users convert their JBoss apps to Geronimo. > > > > There's no need for the creation of a podling for accepting code into > > an existing project, unless you wanted to bring in people and create > > a community around it. We simply need to file an ip-clearance form > > w/ the incubator that notes that we did the due diligence in > > accepting the code. > > > > geir > > > > > > > > On Jan 31, 2007, at 10:10 AM, Filip Hanik - Dev Lists wrote: > > > > > This is the formal vote to accept the J2G codebase and bring it > > > through incubation (see http://marc.theaimsgroup.com/?l=geronimo- > > > dev&m=116906208022256&w=2) > > > The final destination is to be part of the geronimo devtool > > > subproject. > > > (see http://marc.theaimsgroup.com/?l=geronimo- > > > dev&m=116958894929809&w=2) > > > > > > The code donation is located at: > > > https://issues.apache.org/jira/browse/GERONIMO-2743 > > > > > > [ ] +1 lets bring it in, this is great > > > [ ] 0 do what ever you want, not my cup of tea > > > [ ] -1 keep it out of our sight, I have a good reason > > > > > > Optional > > > [ ] I'm willing to mentor this project while it is in incubation > > > [ ] I'm willing to champion the effort while it is in incubation > > > > > > Committers' votes are binding, all other votes will be duly noted > > > > > > Best regards > > > Filip > > > > >
[jira] Closed: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul McMahan closed GERONIMO-2743. -- Resolution: Fixed Fix Version/s: (was: 1.1.x) Assignee: Paul McMahan committed to sandbox, but did not commit the word documents that contain the "IBM Confidential" footer. if one of the contributors wants to remove that footer and reattach then I will commit those to sandbox as well > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik > Assigned To: Paul McMahan >Priority: Minor > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, > J2G-Migration_2.0.0_src_20070302-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Code donation] J2G Conversion tool
Since these are filed under areas available and viewable by an officer, the PMC chair, if so inclined, can keep track of it. On Mar 15, 2007, at 12:55 PM, Paul McMahan wrote: Thanks Jim. For future reference what's the best way to ask for this type of verification? Should we use [EMAIL PROTECTED] Best wishes, Paul On 3/14/07, Jim Jagielski <[EMAIL PROTECTED]> wrote: The IBM and Covalent grants for the J2G Migration toolset (as described here and in https://issues.apache.org/jira/browse/ GERONIMO-2743) have been rec'd and filed.
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks Dims for applying the final patch to the ip clearance form. I notified [EMAIL PROTECTED] and if there are no objections will commit the J2G code to sandbox after the timeframe for lazy consensus has expired (which I was just informed is 72 rather than 48 hours). Best wishes, Paul -- Forwarded message -- From: Paul McMahan <[EMAIL PROTECTED]> Date: Mar 16, 2007 1:41 PM Subject: [IP CLEARANCE] IBM and Covalent contribution of J2G conversion tool To: general@incubator.apache.org IBM and Covalent have donated a JBoss to Geronimo (J2G) application conversion tool to the Apache Geronimo project. - The code was uploaded to Jira issue GERONIMO-2743. [1] - The Geronimo vote to accept the contribution passed. [2] - The IBM and Covalent grants for the J2G Migration toolset have been rec'd and filed [3] - The IP clearance form was added to the Incubator site. [4] Please check the clearance. IIUC the clearance passes by lazy consensus if no -1 votes are cast within the next 48 hours. [1] https://issues.apache.org/jira/browse/GERONIMO-2743 [2] http://tinyurl.com/yve86s [3] http://tinyurl.com/28uodb [4] http://incubator.apache.org/ip-clearance/geronimo-2743-ibm-covalent-j2g.html Best wishes, Paul
Re: [Code donation] J2G Conversion tool
Thanks Jim. For future reference what's the best way to ask for this type of verification? Should we use [EMAIL PROTECTED] Best wishes, Paul On 3/14/07, Jim Jagielski <[EMAIL PROTECTED]> wrote: The IBM and Covalent grants for the J2G Migration toolset (as described here and in https://issues.apache.org/jira/browse/ GERONIMO-2743) have been rec'd and filed.
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks Dims. Now that the paperwork has been ack'd here's the final patch for the IP clearance form. Once that's in place I'll notify [EMAIL PROTECTED] that we're ready to move forward with checking the code into SVN. Best wishes, Paul Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml === --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (revision 518229) +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -94,7 +94,7 @@ - Not yet done + March-13-2007 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the On 3/13/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Paul, I've checked in the xml, generated the html and svn up'ed the incubator site. Should show up on line in a few hours. thanks, dims On 3/7/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > fyi I pinged [EMAIL PROTECTED] for help on patching the IP clearnance > form and resolving the last remaining item on the form. > > Best wishes, > Paul > > On 3/5/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > > Thanks for the feedback Kevan. > > > > Below is a patch for the ip-clearance form that marks three of the > > remaining four items as completed. The last remaining item on the > > form is: > > "Check and make sure that the papers that transfer rights to the ASF > > been received. It is only necessary to transfer rights for the > > package, the core code, and any new code produced by the project." > > > > Can someone help complete this item or provide guidance on how to > > verify the transferal paperwork? > > > > Best wishes, > > Paul > > > > > > Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > > === > > --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > > (revision 514856) > > +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) > > @@ -102,7 +102,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that the files that have been donated have been > > updated to reflect the new ASF copyright. > > @@ -135,7 +135,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that for all items included with the distribution > > that is not under the Apache license, we have the right to combine > > @@ -143,7 +143,7 @@ > > > > > > > > - Not Yet Done. > > + March-5-2007 > > > > Check and > > make sure that all items depended upon by the project is > > covered by one or more of the following approved licenses: Apache, > > > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [Code donation] J2G Conversion tool
The IBM and Covalent grants for the J2G Migration toolset (as described here and in https://issues.apache.org/jira/browse/ GERONIMO-2743) have been rec'd and filed.
Re: [RESULT] VOTE J2G Conversion tool acceptance
Paul, I've checked in the xml, generated the html and svn up'ed the incubator site. Should show up on line in a few hours. thanks, dims On 3/7/07, Paul McMahan <[EMAIL PROTECTED]> wrote: fyi I pinged [EMAIL PROTECTED] for help on patching the IP clearnance form and resolving the last remaining item on the form. Best wishes, Paul On 3/5/07, Paul McMahan <[EMAIL PROTECTED]> wrote: > Thanks for the feedback Kevan. > > Below is a patch for the ip-clearance form that marks three of the > remaining four items as completed. The last remaining item on the > form is: > "Check and make sure that the papers that transfer rights to the ASF > been received. It is only necessary to transfer rights for the > package, the core code, and any new code produced by the project." > > Can someone help complete this item or provide guidance on how to > verify the transferal paperwork? > > Best wishes, > Paul > > > Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > === > --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml > (revision 514856) > +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) > @@ -102,7 +102,7 @@ > > > > - Not Yet Done. > + March-5-2007 > > Check and > make sure that the files that have been donated have been > updated to reflect the new ASF copyright. > @@ -135,7 +135,7 @@ > > > > - Not Yet Done. > + March-5-2007 > > Check and > make sure that for all items included with the distribution > that is not under the Apache license, we have the right to combine > @@ -143,7 +143,7 @@ > > > > - Not Yet Done. > + March-5-2007 > > Check and > make sure that all items depended upon by the project is > covered by one or more of the following approved licenses: Apache, > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
fyi I pinged [EMAIL PROTECTED] for help on patching the IP clearnance form and resolving the last remaining item on the form. Best wishes, Paul On 3/5/07, Paul McMahan <[EMAIL PROTECTED]> wrote: Thanks for the feedback Kevan. Below is a patch for the ip-clearance form that marks three of the remaining four items as completed. The last remaining item on the form is: "Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project." Can someone help complete this item or provide guidance on how to verify the transferal paperwork? Best wishes, Paul Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml === --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (revision 514856) +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -102,7 +102,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. @@ -135,7 +135,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine @@ -143,7 +143,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache,
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks for the feedback Kevan. Below is a patch for the ip-clearance form that marks three of the remaining four items as completed. The last remaining item on the form is: "Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project." Can someone help complete this item or provide guidance on how to verify the transferal paperwork? Best wishes, Paul Index: site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml === --- site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (revision 514856) +++ site-author/ip-clearance/geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -102,7 +102,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. @@ -135,7 +135,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that for all items included with the distribution that is not under the Apache license, we have the right to combine @@ -143,7 +143,7 @@ - Not Yet Done. + March-5-2007 Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache,
Re: [RESULT] VOTE J2G Conversion tool acceptance
On Mar 5, 2007, at 12:08 PM, Paul McMahan wrote: Thanks Jeffrey for updating the JIRA attachment with the ASF copyright headers. Looks good. The next item in the IP clearance form I'm looking at is: "Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms." The J2G zip contains a few non-ASF jars. I think these are all BSD compatible, anyone disagree? dom4j-1.6.1.jar jaxen-1.1-beta-6.jar junit-3.8.1.jar I would assume junit is a build time dependency. We already embed jaxen in Geronimo. dom4j looks ok. I'm not sure about this one: pull-parser-2.1.10.jar Some googling turned up this license which looks BSD compatible: http://www.extreme.indiana.edu/xgws/xsoap/xpp/download/ PullParser2/LICENSE.txt Anyone familiar with PullParser know if this is the right one? Ya. Looks ok. We currently include xpp3 (also produced by IU Extreme! Lab). Looks like the same license... --kevan
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks Jeffrey for updating the JIRA attachment with the ASF copyright headers. Looks good. The next item in the IP clearance form I'm looking at is: "Check and make sure that all items depended upon by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms." The J2G zip contains a few non-ASF jars. I think these are all BSD compatible, anyone disagree? dom4j-1.6.1.jar jaxen-1.1-beta-6.jar junit-3.8.1.jar I'm not sure about this one: pull-parser-2.1.10.jar Some googling turned up this license which looks BSD compatible: http://www.extreme.indiana.edu/xgws/xsoap/xpp/download/PullParser2/LICENSE.txt Anyone familiar with PullParser know if this is the right one? Best wishes, Paul On 3/2/07, Paul McMahan <[EMAIL PROTECTED]> wrote: One of the remaining items on the IP clearance form is: "Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright." I updated https://issues.apache.org/jira/browse/GERONIMO-2743 with a list of files that don't contain an ASF copyright header. Best wishes, Paul On 3/2/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > any thoughts on when the PMC will have time to look/comment/approve the > remaining items on this donation > > Filip > > Davanum Srinivas wrote: > > Filip, > > > > There are 6 items under "Copyright" and "Verify distribution rights". > > Someone on the pmc needs to deal with them and send an updated patch. > > At least the first 2 under "Verify distribution rights" can be marked > > "Not Applicable". > > > > thanks, > > dims > > > > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > >> cool, sorry to bug, but is there anything more you need from us? > >> > >> Filip > >> > >> Davanum Srinivas wrote: > >> > Checked in. > >> > > >> > thanks, > >> > dims > >> > > >> > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > >> >> dims, > >> >> I've updated some info in the IP clearance form, attached is the > >> >> patch file. > >> >> The JIRA has also been updated with the codebase that reflects the > >> ASF > >> >> license in the source header, and the IBM copyright in the > >> COPYRIGHT.txt > >> >> file > >> >> Both Covalent and IBM CCLA are also attached to the JIRA item. > >> >> > >> >> Is there anything left from us, or is the rest left up to the > >> >> Geronimo PMC? > >> >> > >> >> Filip > >> > >> > > > > > >
[jira] Updated: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2743: -- Attachment: J2G-Migration_2.0.0_src_20070302-1501.zip Files listed by Paul has been updated to reflect the new ASF copyright. > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik >Priority: Minor > Fix For: 1.1.x > > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip, > J2G-Migration_2.0.0_src_20070302-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] VOTE J2G Conversion tool acceptance
Doing this today Filip. On Mar 2, 2007, at 10:20 AM, Filip Hanik - Dev Lists wrote: any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: Filip, There are 6 items under "Copyright" and "Verify distribution rights". Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under "Verify distribution rights" can be marked "Not Applicable". thanks, dims On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: > Checked in. > > thanks, > dims > > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: >> dims, >> I've updated some info in the IP clearance form, attached is the >> patch file. >> The JIRA has also been updated with the codebase that reflects the ASF >> license in the source header, and the IBM copyright in the COPYRIGHT.txt >> file >> Both Covalent and IBM CCLA are also attached to the JIRA item. >> >> Is there anything left from us, or is the rest left up to the >> Geronimo PMC? >> >> Filip
Re: [RESULT] VOTE J2G Conversion tool acceptance
One of the remaining items on the IP clearance form is: "Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright." I updated https://issues.apache.org/jira/browse/GERONIMO-2743 with a list of files that don't contain an ASF copyright header. Best wishes, Paul On 3/2/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: > Filip, > > There are 6 items under "Copyright" and "Verify distribution rights". > Someone on the pmc needs to deal with them and send an updated patch. > At least the first 2 under "Verify distribution rights" can be marked > "Not Applicable". > > thanks, > dims > > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: >> cool, sorry to bug, but is there anything more you need from us? >> >> Filip >> >> Davanum Srinivas wrote: >> > Checked in. >> > >> > thanks, >> > dims >> > >> > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: >> >> dims, >> >> I've updated some info in the IP clearance form, attached is the >> >> patch file. >> >> The JIRA has also been updated with the codebase that reflects the >> ASF >> >> license in the source header, and the IBM copyright in the >> COPYRIGHT.txt >> >> file >> >> Both Covalent and IBM CCLA are also attached to the JIRA item. >> >> >> >> Is there anything left from us, or is the rest left up to the >> >> Geronimo PMC? >> >> >> >> Filip >> >> > >
[jira] Commented: (GERONIMO-2743) [Code donation] J2G Conversion tool
/security-plugin/src/commons-logging.properties src2/security-plugin/test-apps/security/geronimo-secutiry-plan.xml src2/security-plugin/test-apps/security/login-config.xml src2/security-plugin/test-apps/security/security-geronimo-plan.xml src2/web-migration-plugin/build.properties src2/web-migration-plugin/plugin.xml src2/web-migration-plugin/src/commons-logging.properties src2/web-migration-plugin/test-resources/jboss-web.xml src2/xml-conversion-helper/.settings/org.eclipse.ltk.core.refactoring.prefs src2/xml-conversion-helper/build.properties src2/xml-conversion-helper/plugin.xml src2/xml-conversion-helper/src/commons-logging.properties > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik >Priority: Minor > Fix For: 1.1.x > > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] VOTE J2G Conversion tool acceptance
any thoughts on when the PMC will have time to look/comment/approve the remaining items on this donation Filip Davanum Srinivas wrote: Filip, There are 6 items under "Copyright" and "Verify distribution rights". Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under "Verify distribution rights" can be marked "Not Applicable". thanks, dims On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: > Checked in. > > thanks, > dims > > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: >> dims, >> I've updated some info in the IP clearance form, attached is the >> patch file. >> The JIRA has also been updated with the codebase that reflects the ASF >> license in the source header, and the IBM copyright in the COPYRIGHT.txt >> file >> Both Covalent and IBM CCLA are also attached to the JIRA item. >> >> Is there anything left from us, or is the rest left up to the >> Geronimo PMC? >> >> Filip
Re: [RESULT] VOTE J2G Conversion tool acceptance
Filip, There are 6 items under "Copyright" and "Verify distribution rights". Someone on the pmc needs to deal with them and send an updated patch. At least the first 2 under "Verify distribution rights" can be marked "Not Applicable". thanks, dims On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: > Checked in. > > thanks, > dims > > On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: >> dims, >> I've updated some info in the IP clearance form, attached is the >> patch file. >> The JIRA has also been updated with the codebase that reflects the ASF >> license in the source header, and the IBM copyright in the COPYRIGHT.txt >> file >> Both Covalent and IBM CCLA are also attached to the JIRA item. >> >> Is there anything left from us, or is the rest left up to the >> Geronimo PMC? >> >> Filip -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
cool, sorry to bug, but is there anything more you need from us? Filip Davanum Srinivas wrote: Checked in. thanks, dims On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip
Re: [RESULT] VOTE J2G Conversion tool acceptance
Checked in. thanks, dims On 2/26/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip Davanum Srinivas wrote: > Yes, i can help with the ip-clearance. > > -- dims > > On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: >> >> On Feb 19, 2007, at 9:47 AM, Matt Hogstrom wrote: >> >> > So, we voted this monster in and accepted the code base. At this >> > point, per Geir's note in this thread Noted below: >> > >> > >> > > Here's the process : >> > > >> > > 1) Contributor offers code *Complete* >> > > >> > > 2) Project decides to accept or reject code. Formally, this is >> > the PMC, but everyone should chime in. *Complete* per vote below >> > > >> > > 3) Contributor provides CCLA >> > *Complete* CCLA located in JIRA >> > >> > > Cleans up code to remove copyright statements >> > *Outstanding* Need a volunteer here. I think ideally the >> > contributor would accomplish this step and post an updated file in >> > the JIRA with this work completed. >> > >> > > And puts the standard apache file header in place. >> > *Outstanding* Really same as above. Needs to have a committer >> > review this so need a new volunteer here. >> > >> > > >> > > 4) Project accepts code contribution and registers the code >> > contribution w/ the incubator with an ip_clearance form : http:// >> > svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ >> > *Outstanding* We've already accepted the code through this vote. >> > This is the mechanics of getting the code into Apache. I think the >> > committer noted above should do this as well. >> >> Matt, committers can certainly help. However, either an officer (you) >> or an ASF member (Dims or Geir) will need to fill out and submit the >> IP Clearance form -- http://incubator.apache.org/ip-clearance/ip- >> clearance-template.html. Also, the software grant form needs to be >> acknowledged by the ASF secretary (or another ASF officer). >> >> --kevan >> >> >> >> >> >> > > Index: geronimo-2743-ibm-covalent-j2g.xml === --- geronimo-2743-ibm-covalent-j2g.xml (revision 511944) +++ geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -35,7 +35,7 @@ Project info - Which PMC will be responsible for the code : Apache Geronimo + Which PMC will be responsible for the code : Apache Geronimo @@ -59,15 +59,28 @@ - Not Applicable +January-16-2007 - - - If applicable, make sure that any associated name does not already -exist and check www.nameprotect.com to be sure that the name is not -already trademarked for an existing software product. - +JIRA https://issues.apache.org/jira/browse/GERONIMO-2743";>GERONIMO-2743 Created. + https://issues.apache.org/jira/secure/attachment/12349176/Covalent-J2G-Tool.pdf"Covalent CCLA Attached + https://issues.apache.org/jira/secure/attachment/12349047/CCLA.tif";>IBM CCLA Attached + https://issues.apache.org/jira/secure/attachment/12349046/J2G-Migration-v2_src_1.0.0.zip";>Original codebase attached + + + +February-21-2007 + +Copyright adjusted and https://issues.apache.org/jira/secure/attachment/12351724/J2G-Migration_2.0.0_src_20070220-1501.zip";>codebase cleaned up, ready for import + + + February-21-2007 + +MD5 or SHA1 sum for donated software: + 3cfbefd2424c3556fdcbf162a1129399 *J2G-Migration_2.0.0_src_20070220-1501.zip + e49e61df710dae15025b0126e4f8e672 *J2G-Migration-v2_src_1.0.0.zip + (Note versioned software used to calculate sum in parentheses). + Copyright @@ -80,7 +93,7 @@ - Not Yet Done. + Not yet done Check and make sure that the papers that transfer rights to the ASF been received. It is
[jira] Commented: (GERONIMO-2743) [Code donation] J2G Conversion tool
[
https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475973
]
Paul McMahan commented on GERONIMO-2743:
There was some discussion about the package name on dev:
http://www.nabble.com/-VOTE--J2G-Conversion-tool-acceptance-tf3149274.html#a9120007
Specifically, Sachin said:
{quote}
In order to follow proper convention, the package names need to start with the
plugin id and the plugin id should be organization + product + plugin so in our
case...
plugin id: org.apache.geronimo.j2g.someIdForThisSpecificPlugin
and all packages within that plugin should start with the pluginId
{quote}
Since this probably constitutes a significant amount of refactoring (and maybe
even some more discussion) I think it might be best to make the packaging
adjustments after the code is in sandbox.
> [Code donation] J2G Conversion tool
> ---
>
> Key: GERONIMO-2743
> URL: https://issues.apache.org/jira/browse/GERONIMO-2743
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
>Affects Versions: 1.1.x
> Environment: MS Windows XP SP2 (although Java based should work on
> any OS supporting Java)
>Reporter: Filip Hanik
>Priority: Minor
> Fix For: 1.1.x
>
> Attachments: CCLA.tif, Covalent-J2G-Tool.pdf,
> J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip
>
>
> IBM has together with in a joint effort with Covalent developed a JBoss to
> Geronimo conversion tool. This tool is used when converting applications from
> JBoss to Geronimo, and automatically converts the configuration file from one
> app server to the other.
> We feel that this piece of software adds value to Geronimo and users adopting
> Geronimo and would like to see this effort continue as part of the Geronimo
> project, a plugin or a sub project of Geronimo.
> The initial donation is for version 1.0 of this tool, and while a 1.1 is in
> the making to improve 1.0, 1.1 is not yet complete but will be donated as
> soon as the community feels that this tool belongs at the ASF, more
> specifically within the Geronimo project.
> If you'd think this tool is valuable, but believe it should go through
> incubation, we would hope that a Geronimo committer would step up and
> champion this effort.
> The tool, including IBM's CCLA, can be found at
> http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA
> upon request)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475934 ] Filip Hanik commented on GERONIMO-2743: --- Current codebase is packaged as: org.apache.apps.j2gmigrator... we suggest that during the import, the code is restructured as: org.apache.geronimo.j2gmigrator or org.apache.geronimo.devtools.j2gmigrator > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik >Priority: Minor > Fix For: 1.1.x > > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] VOTE J2G Conversion tool acceptance
dims, I've updated some info in the IP clearance form, attached is the patch file. The JIRA has also been updated with the codebase that reflects the ASF license in the source header, and the IBM copyright in the COPYRIGHT.txt file Both Covalent and IBM CCLA are also attached to the JIRA item. Is there anything left from us, or is the rest left up to the Geronimo PMC? Filip Davanum Srinivas wrote: Yes, i can help with the ip-clearance. -- dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: On Feb 19, 2007, at 9:47 AM, Matt Hogstrom wrote: > So, we voted this monster in and accepted the code base. At this > point, per Geir's note in this thread Noted below: > > > > Here's the process : > > > > 1) Contributor offers code *Complete* > > > > 2) Project decides to accept or reject code. Formally, this is > the PMC, but everyone should chime in. *Complete* per vote below > > > > 3) Contributor provides CCLA > *Complete* CCLA located in JIRA > > > Cleans up code to remove copyright statements > *Outstanding* Need a volunteer here. I think ideally the > contributor would accomplish this step and post an updated file in > the JIRA with this work completed. > > > And puts the standard apache file header in place. > *Outstanding* Really same as above. Needs to have a committer > review this so need a new volunteer here. > > > > > 4) Project accepts code contribution and registers the code > contribution w/ the incubator with an ip_clearance form : http:// > svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ > *Outstanding* We've already accepted the code through this vote. > This is the mechanics of getting the code into Apache. I think the > committer noted above should do this as well. Matt, committers can certainly help. However, either an officer (you) or an ASF member (Dims or Geir) will need to fill out and submit the IP Clearance form -- http://incubator.apache.org/ip-clearance/ip- clearance-template.html. Also, the software grant form needs to be acknowledged by the ASF secretary (or another ASF officer). --kevan Index: geronimo-2743-ibm-covalent-j2g.xml === --- geronimo-2743-ibm-covalent-j2g.xml (revision 511944) +++ geronimo-2743-ibm-covalent-j2g.xml (working copy) @@ -35,7 +35,7 @@ Project info - Which PMC will be responsible for the code : Apache Geronimo + Which PMC will be responsible for the code : Apache Geronimo @@ -59,15 +59,28 @@ - Not Applicable +January-16-2007 - - - If applicable, make sure that any associated name does not already -exist and check www.nameprotect.com to be sure that the name is not -already trademarked for an existing software product. - +JIRA https://issues.apache.org/jira/browse/GERONIMO-2743";>GERONIMO-2743 Created. + https://issues.apache.org/jira/secure/attachment/12349176/Covalent-J2G-Tool.pdf"Covalent CCLA Attached + https://issues.apache.org/jira/secure/attachment/12349047/CCLA.tif";>IBM CCLA Attached + https://issues.apache.org/jira/secure/attachment/12349046/J2G-Migration-v2_src_1.0.0.zip";>Original codebase attached + + + +February-21-2007 + +Copyright adjusted and https://issues.apache.org/jira/secure/attachment/12351724/J2G-Migration_2.0.0_src_20070220-1501.zip";>codebase cleaned up, ready for import + + + February-21-2007 + +MD5 or SHA1 sum for donated software: + 3cfbefd2424c3556fdcbf162a1129399 *J2G-Migration_2.0.0_src_20070220-1501.zip + e49e61df710dae15025b0126e4f8e672 *J2G-Migration-v2_src_1.0.0.zip + (Note versioned software used to calculate sum in parentheses). + Copyright @@ -80,7 +93,7 @@ - Not Yet Done. + Not yet done Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the @@ -107,13 +120,13 @@ -
Re: [RESULT] VOTE J2G Conversion tool acceptance
In order to follow proper convention, the package names need to start with the plugin id and the plugin id should be organization + product + plugin so in our case... plugin id: org.apache.geronimo.j2g.someIdForThisSpecificPlugin and all packages within that plugin should start with the pluginId. -sachin On Feb 23, 2007, at 9:37 AM, Matt Hogstrom wrote: BTW, One thing I noticed in the new attachment is that the java package names have been changed from com.ibm.j2g to org.apache.apps.j2g. That's an improvement, I think. I think org.apache.geronimo.tools.j2g would probably make more sense. We can do that refactoring afterwards though.
Re: [RESULT] VOTE J2G Conversion tool acceptance
On Feb 22, 2007, at 12:36 PM, Paul McMahan wrote: BTW, One thing I noticed in the new attachment is that the java package names have been changed from com.ibm.j2g to org.apache.apps.j2g. That's an improvement, I think. I think org.apache.geronimo.tools.j2g would probably make more sense. We can do that refactoring afterwards though. But I wanted to mention this in context of this thread in case anyone has concerns about it. Also, the page footer on some of the documentation says "IBM Confidential". That was probably just an oversight but I don't think those docs should be committed to SVN unless the contributor removes the footer. I agree with removing the Confidential part. Best wishes, Paul On 2/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Added an xml here: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ip- clearance/ When there is an update to that doc, Anyone of us can update the doc and re-publish the html. Someone needs to shepherd the process though. See the items on the list for TODO's. thanks, dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Feb 19, 2007, at 11:22 AM, Davanum Srinivas wrote: > > > Yes, i can help with the ip-clearance. > > Thanks Dims! > --kevan > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
I say go ahead and commit it, and I can run through add fix the manifests if you want, should take like 5 min using the manifest editor. -sachin On Feb 22, 2007, at 12:36 PM, Paul McMahan wrote: Thanks to Dims for adding the XML for an IP clearance form. A new attachment on the JIRA addresses the copyright header issues, so once the IP clearance form is completed and the software grant form has been ACK'd I am ready to commit to ASF's SVN repo. IIUC I can't do much to help with the paperwork since I'm not an ASF member or officer, but if I can in fact help then please don't hesitate to let me know. BTW, One thing I noticed in the new attachment is that the java package names have been changed from com.ibm.j2g to org.apache.apps.j2g. That's an improvement, I think. But the various scripts, documentation, and eclipse plugin metadata files in the src package were not updated to match this change, rendering major parts of the contribution non-functional. I don't think this should necessarily prevent us from committing the code to sandbox, because it shouldn't be too hard to fix. But I wanted to mention this in context of this thread in case anyone has concerns about it. Also, the page footer on some of the documentation says "IBM Confidential". That was probably just an oversight but I don't think those docs should be committed to SVN unless the contributor removes the footer. Best wishes, Paul On 2/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Added an xml here: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ip- clearance/ When there is an update to that doc, Anyone of us can update the doc and re-publish the html. Someone needs to shepherd the process though. See the items on the list for TODO's. thanks, dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Feb 19, 2007, at 11:22 AM, Davanum Srinivas wrote: > > > Yes, i can help with the ip-clearance. > > Thanks Dims! > --kevan > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
Thanks to Dims for adding the XML for an IP clearance form. A new attachment on the JIRA addresses the copyright header issues, so once the IP clearance form is completed and the software grant form has been ACK'd I am ready to commit to ASF's SVN repo. IIUC I can't do much to help with the paperwork since I'm not an ASF member or officer, but if I can in fact help then please don't hesitate to let me know. BTW, One thing I noticed in the new attachment is that the java package names have been changed from com.ibm.j2g to org.apache.apps.j2g. That's an improvement, I think. But the various scripts, documentation, and eclipse plugin metadata files in the src package were not updated to match this change, rendering major parts of the contribution non-functional. I don't think this should necessarily prevent us from committing the code to sandbox, because it shouldn't be too hard to fix. But I wanted to mention this in context of this thread in case anyone has concerns about it. Also, the page footer on some of the documentation says "IBM Confidential". That was probably just an oversight but I don't think those docs should be committed to SVN unless the contributor removes the footer. Best wishes, Paul On 2/19/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: Added an xml here: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ When there is an update to that doc, Anyone of us can update the doc and re-publish the html. Someone needs to shepherd the process though. See the items on the list for TODO's. thanks, dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Feb 19, 2007, at 11:22 AM, Davanum Srinivas wrote: > > > Yes, i can help with the ip-clearance. > > Thanks Dims! > --kevan > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
[jira] Updated: (GERONIMO-2743) [Code donation] J2G Conversion tool
[ https://issues.apache.org/jira/browse/GERONIMO-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeffrey Faelnar updated GERONIMO-2743: -- Attachment: J2G-Migration_2.0.0_src_20070220-1501.zip The JIRA has been updated with the copyrights fixed and packages renamed. > [Code donation] J2G Conversion tool > --- > > Key: GERONIMO-2743 > URL: https://issues.apache.org/jira/browse/GERONIMO-2743 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) >Affects Versions: 1.1.x > Environment: MS Windows XP SP2 (although Java based should work on > any OS supporting Java) >Reporter: Filip Hanik >Priority: Minor > Fix For: 1.1.x > > Attachments: CCLA.tif, Covalent-J2G-Tool.pdf, > J2G-Migration-v2_src_1.0.0.zip, J2G-Migration_2.0.0_src_20070220-1501.zip > > > IBM has together with in a joint effort with Covalent developed a JBoss to > Geronimo conversion tool. This tool is used when converting applications from > JBoss to Geronimo, and automatically converts the configuration file from one > app server to the other. > We feel that this piece of software adds value to Geronimo and users adopting > Geronimo and would like to see this effort continue as part of the Geronimo > project, a plugin or a sub project of Geronimo. > The initial donation is for version 1.0 of this tool, and while a 1.1 is in > the making to improve 1.0, 1.1 is not yet complete but will be donated as > soon as the community feels that this tool belongs at the ASF, more > specifically within the Geronimo project. > If you'd think this tool is valuable, but believe it should go through > incubation, we would hope that a Geronimo committer would step up and > champion this effort. > The tool, including IBM's CCLA, can be found at > http://people.apache.org/~fhanik/j2g/j2g.html (Covalent will file the CCLA > upon request) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [RESULT] VOTE J2G Conversion tool acceptance
On Feb 19, 2007, at 11:09 AM, Kevan Miller wrote: Matt, committers can certainly help. However, either an officer (you) or an ASF member (Dims or Geir) will need to fill out and submit the IP Clearance form -- http://incubator.apache.org/ip- clearance/ip-clearance-template.html. Also, the software grant form needs to be acknowledged by the ASF secretary (or another ASF officer). I figured it would be one of the three of us :) although the train seemed to be stopped at Copyright station.
Re: [RESULT] VOTE J2G Conversion tool acceptance
Added an xml here: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ When there is an update to that doc, Anyone of us can update the doc and re-publish the html. Someone needs to shepherd the process though. See the items on the list for TODO's. thanks, dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: On Feb 19, 2007, at 11:22 AM, Davanum Srinivas wrote: > Yes, i can help with the ip-clearance. Thanks Dims! --kevan -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
On Feb 19, 2007, at 11:22 AM, Davanum Srinivas wrote: Yes, i can help with the ip-clearance. Thanks Dims! --kevan
Re: [RESULT] VOTE J2G Conversion tool acceptance
Yes, i can help with the ip-clearance. -- dims On 2/19/07, Kevan Miller <[EMAIL PROTECTED]> wrote: On Feb 19, 2007, at 9:47 AM, Matt Hogstrom wrote: > So, we voted this monster in and accepted the code base. At this > point, per Geir's note in this thread Noted below: > > > > Here's the process : > > > > 1) Contributor offers code *Complete* > > > > 2) Project decides to accept or reject code. Formally, this is > the PMC, but everyone should chime in. *Complete* per vote below > > > > 3) Contributor provides CCLA > *Complete* CCLA located in JIRA > > > Cleans up code to remove copyright statements > *Outstanding* Need a volunteer here. I think ideally the > contributor would accomplish this step and post an updated file in > the JIRA with this work completed. > > > And puts the standard apache file header in place. > *Outstanding* Really same as above. Needs to have a committer > review this so need a new volunteer here. > > > > > 4) Project accepts code contribution and registers the code > contribution w/ the incubator with an ip_clearance form : http:// > svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ > *Outstanding* We've already accepted the code through this vote. > This is the mechanics of getting the code into Apache. I think the > committer noted above should do this as well. Matt, committers can certainly help. However, either an officer (you) or an ASF member (Dims or Geir) will need to fill out and submit the IP Clearance form -- http://incubator.apache.org/ip-clearance/ip- clearance-template.html. Also, the software grant form needs to be acknowledged by the ASF secretary (or another ASF officer). --kevan -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
Re: [RESULT] VOTE J2G Conversion tool acceptance
On Feb 19, 2007, at 9:47 AM, Matt Hogstrom wrote: So, we voted this monster in and accepted the code base. At this point, per Geir's note in this thread Noted below: > Here's the process : > > 1) Contributor offers code *Complete* > > 2) Project decides to accept or reject code. Formally, this is the PMC, but everyone should chime in. *Complete* per vote below > > 3) Contributor provides CCLA *Complete* CCLA located in JIRA > Cleans up code to remove copyright statements *Outstanding* Need a volunteer here. I think ideally the contributor would accomplish this step and post an updated file in the JIRA with this work completed. > And puts the standard apache file header in place. *Outstanding* Really same as above. Needs to have a committer review this so need a new volunteer here. > > 4) Project accepts code contribution and registers the code contribution w/ the incubator with an ip_clearance form : http:// svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ *Outstanding* We've already accepted the code through this vote. This is the mechanics of getting the code into Apache. I think the committer noted above should do this as well. Matt, committers can certainly help. However, either an officer (you) or an ASF member (Dims or Geir) will need to fill out and submit the IP Clearance form -- http://incubator.apache.org/ip-clearance/ip- clearance-template.html. Also, the software grant form needs to be acknowledged by the ASF secretary (or another ASF officer). --kevan
Re: [RESULT] VOTE J2G Conversion tool acceptance
Matt Hogstrom <[EMAIL PROTECTED]> wrote on 02/19/2007 06:47:45 AM: > So, we voted this monster in and accepted the code base. At this > point, per Geir's note in this thread Noted below: > > > > Here's the process : > > > > 1) Contributor offers code *Complete* > > > > 2) Project decides to accept or reject code. Formally, this is > the PMC, but everyone should chime in. *Complete* per vote below > > > > 3) Contributor provides CCLA > *Complete* CCLA located in JIRA > > > Cleans up code to remove copyright statements > *Outstanding* Need a volunteer here. I think ideally the contributor > would accomplish this step and post an updated file in the JIRA with > this work completed. > > > And puts the standard apache file header in place. > *Outstanding* Really same as above. Needs to have a committer review > this so need a new volunteer here. > > > > > 4) Project accepts code contribution and registers the code > contribution w/ the incubator with an ip_clearance form : http:// > svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ > *Outstanding* We've already accepted the code through this vote. > This is the mechanics of getting the code into Apache. I think the > committer noted above should do this as well. > > At this point I think Filip would take care of the Copyrights My team will take the lead and take care or the Copyrights and submit a patched bundle. Michael Malgeri >and > someone on the project (volunteers needed) would take care of the > final clearance and commit. > > For its placement in Geronimo I would think sandbox is the right > place for this to start with. > > Thoughts, volunteers ? > > > > > On Feb 2, 2007, at 10:01 AM, Filip Hanik - Dev Lists wrote: > > > >> Here is the result: > >> > >> +1; > >> Jeff Genender > >> Paul McMahan > >> Kevan Miller > >> Prasad Kashyap > >> Hernan Cunico > >> Dain Sundstrom > >> David Jencks > >> Cris Cardona > >> Aaron Mulder > >> David Blevins > >> Anita Kulshreshtha > >> Gianny Damour > >> Rick McGuire > >> Matt Hogstrom > >> Sachin Patel > >> Vamsi Reddy > >> > >> No 0's and no -1's. > >> We will start filling out the IP clearance form, and attach it to > >> the JIRA item along with the updated codebase. > >> We will use this template > >> http://incubator.apache.org/ip-clearance/ip-clearance-template.html > >> > >> Once this has been done, we will bring the JIRA to the attention > >> of the G committers for review. > >> > >> Filip >
Re: [RESULT] VOTE J2G Conversion tool acceptance
I agree here and just let me know anything I can do to help as well. Jeff Paul McMahan wrote: > During the vote Jeff and I volunteered to help mentor this code > contribution. Like you pointed out, the process outlined in Geir's > note has the contributor replacing the copyright statements and not > the recipient, which makes sense to me from a legal perspective. Once > that is in place I would be happy to help with the ip_clearance form > and committing the code into sandbox. > > Best wishes, > Paul > > On 2/19/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: >> So, we voted this monster in and accepted the code base. At this >> point, per Geir's note in this thread Noted below: >> >> >> > Here's the process : >> > >> > 1) Contributor offers code *Complete* >> > >> > 2) Project decides to accept or reject code. Formally, this is >> the PMC, but everyone should chime in. *Complete* per vote below >> > >> > 3) Contributor provides CCLA >> *Complete* CCLA located in JIRA >> >> > Cleans up code to remove copyright statements >> *Outstanding* Need a volunteer here. I think ideally the contributor >> would accomplish this step and post an updated file in the JIRA with >> this work completed. >> >> > And puts the standard apache file header in place. >> *Outstanding* Really same as above. Needs to have a committer review >> this so need a new volunteer here. >> >> > >> > 4) Project accepts code contribution and registers the code >> contribution w/ the incubator with an ip_clearance form : http:// >> svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ >> *Outstanding* We've already accepted the code through this vote. >> This is the mechanics of getting the code into Apache. I think the >> committer noted above should do this as well. >> >> At this point I think Filip would take care of the Copyrights and >> someone on the project (volunteers needed) would take care of the >> final clearance and commit. >> >> For its placement in Geronimo I would think sandbox is the right >> place for this to start with. >> >> Thoughts, volunteers ? >> >> >> >> > On Feb 2, 2007, at 10:01 AM, Filip Hanik - Dev Lists wrote: >> > >> >> Here is the result: >> >> >> >> +1; >> >> Jeff Genender >> >> Paul McMahan >> >> Kevan Miller >> >> Prasad Kashyap >> >> Hernan Cunico >> >> Dain Sundstrom >> >> David Jencks >> >> Cris Cardona >> >> Aaron Mulder >> >> David Blevins >> >> Anita Kulshreshtha >> >> Gianny Damour >> >> Rick McGuire >> >> Matt Hogstrom >> >> Sachin Patel >> >> Vamsi Reddy >> >> >> >> No 0's and no -1's. >> >> We will start filling out the IP clearance form, and attach it to >> >> the JIRA item along with the updated codebase. >> >> We will use this template >> >> http://incubator.apache.org/ip-clearance/ip-clearance-template.html >> >> >> >> Once this has been done, we will bring the JIRA to the attention >> >> of the G committers for review. >> >> >> >> Filip >> >>
Re: [RESULT] VOTE J2G Conversion tool acceptance
During the vote Jeff and I volunteered to help mentor this code contribution. Like you pointed out, the process outlined in Geir's note has the contributor replacing the copyright statements and not the recipient, which makes sense to me from a legal perspective. Once that is in place I would be happy to help with the ip_clearance form and committing the code into sandbox. Best wishes, Paul On 2/19/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote: So, we voted this monster in and accepted the code base. At this point, per Geir's note in this thread Noted below: > Here's the process : > > 1) Contributor offers code *Complete* > > 2) Project decides to accept or reject code. Formally, this is the PMC, but everyone should chime in. *Complete* per vote below > > 3) Contributor provides CCLA *Complete* CCLA located in JIRA > Cleans up code to remove copyright statements *Outstanding* Need a volunteer here. I think ideally the contributor would accomplish this step and post an updated file in the JIRA with this work completed. > And puts the standard apache file header in place. *Outstanding* Really same as above. Needs to have a committer review this so need a new volunteer here. > > 4) Project accepts code contribution and registers the code contribution w/ the incubator with an ip_clearance form : http:// svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ *Outstanding* We've already accepted the code through this vote. This is the mechanics of getting the code into Apache. I think the committer noted above should do this as well. At this point I think Filip would take care of the Copyrights and someone on the project (volunteers needed) would take care of the final clearance and commit. For its placement in Geronimo I would think sandbox is the right place for this to start with. Thoughts, volunteers ? > On Feb 2, 2007, at 10:01 AM, Filip Hanik - Dev Lists wrote: > >> Here is the result: >> >> +1; >> Jeff Genender >> Paul McMahan >> Kevan Miller >> Prasad Kashyap >> Hernan Cunico >> Dain Sundstrom >> David Jencks >> Cris Cardona >> Aaron Mulder >> David Blevins >> Anita Kulshreshtha >> Gianny Damour >> Rick McGuire >> Matt Hogstrom >> Sachin Patel >> Vamsi Reddy >> >> No 0's and no -1's. >> We will start filling out the IP clearance form, and attach it to >> the JIRA item along with the updated codebase. >> We will use this template >> http://incubator.apache.org/ip-clearance/ip-clearance-template.html >> >> Once this has been done, we will bring the JIRA to the attention >> of the G committers for review. >> >> Filip
Re: [RESULT] VOTE J2G Conversion tool acceptance
So, we voted this monster in and accepted the code base. At this point, per Geir's note in this thread Noted below: > Here's the process : > > 1) Contributor offers code *Complete* > > 2) Project decides to accept or reject code. Formally, this is the PMC, but everyone should chime in. *Complete* per vote below > > 3) Contributor provides CCLA *Complete* CCLA located in JIRA > Cleans up code to remove copyright statements *Outstanding* Need a volunteer here. I think ideally the contributor would accomplish this step and post an updated file in the JIRA with this work completed. > And puts the standard apache file header in place. *Outstanding* Really same as above. Needs to have a committer review this so need a new volunteer here. > > 4) Project accepts code contribution and registers the code contribution w/ the incubator with an ip_clearance form : http:// svn.apache.org/viewvc/incubator/public/trunk/site-author/ip-clearance/ *Outstanding* We've already accepted the code through this vote. This is the mechanics of getting the code into Apache. I think the committer noted above should do this as well. At this point I think Filip would take care of the Copyrights and someone on the project (volunteers needed) would take care of the final clearance and commit. For its placement in Geronimo I would think sandbox is the right place for this to start with. Thoughts, volunteers ? On Feb 2, 2007, at 10:01 AM, Filip Hanik - Dev Lists wrote: Here is the result: +1; Jeff Genender Paul McMahan Kevan Miller Prasad Kashyap Hernan Cunico Dain Sundstrom David Jencks Cris Cardona Aaron Mulder David Blevins Anita Kulshreshtha Gianny Damour Rick McGuire Matt Hogstrom Sachin Patel Vamsi Reddy No 0's and no -1's. We will start filling out the IP clearance form, and attach it to the JIRA item along with the updated codebase. We will use this template http://incubator.apache.org/ip-clearance/ip-clearance-template.html Once this has been done, we will bring the JIRA to the attention of the G committers for review. Filip
Re: Conversion Tool
and.java:60) > at java.lang.Thread.run(Thread.java:595)I have placed the plan file > and ear that I am using at the following location... > > http://people.apache.org/~cjblythe/m2_deploy/ > > Thanks... > > Chris > > > On 2/14/07, David Blevins < [EMAIL PROTECTED]> wrote: > On Feb 14, 2007, at 1:59 PM, Christopher Blythe wrote: > > > Dain and David... > > > > Took a swag at deploying Daytrader on Geronimo 2.0-M2... During > > deployment, it complained about the openejb-jar.xml file missing > > from the EJB module. I added the one you provided earlier in this > > chain, but for some reason it is still complaining that the openejb- > > jar.xml file is missing from the EJB module. I think Matt is > > probably running into the same issue... > > > > Does the or-mapping file also need to go in the ear/jar somewhere? > > Should this work on M2? Is there anything else that needs to go > > into the jar/ear? > > > > It really seems to me like we need way too many extra xml files to > > deploy this thing. > > You shouldn't need any files in the ear, i.e. passing the plan as a > parameter on the command line should work as always. > > Post the message text and a stack trace (if there is one) and I'll > see if I can't find what part of the code is confused. > > -David > > > > > Thanks... > > > > Chris > > > > > > > > > > > > On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:I just fix that > > allows nested openejb plans to work correctly. This > > was a big problem in the tck since all plans use the nested model. > > > > -dain > > > > On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > > > > > OK, I think the conversion tool should be full working now. > > > > > > There were loads of tiny bugs causing deployments to fail > > > especially around cmp. I tested the converter with the OpenEJB2 > > > itests which use almost every feature of OpenEJB2 and the > > > application now deploys with out error now. Of course there are > > > things sill unimplemented or ported to 3, so if you try to use > > > those features, you will get an exception at runtime. > > > > > > Let us know if you find any problems with the converter. > > > > > > -dain > > > > > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > > > > > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: > > >> > > >>> Haven't been able to get a full deploy of anything (tried > > >>> daytrader and the v2 itests), but things are starting to look > > >>> good with the converter. The basic conversion is happening and > > >>> conversion of things like environment and abstract name queries > > >>> are definitely getting ported over. Still see some hiccups in > > >>> CMPs, but apps without CMPs may deploy just fine. Will look > into > > >>> it more when I get up. > > >>> > > >>> Dain, can you take a look at the persistence unit part of the > > >>> rewritten EjbModuleBuilder. Seems something in the way i've > > >>> reworked the code results in those not coming through so well. > > >> > > >> Looking at it now. > > >> > > >> -dain > > >> > > > > > > > > > > > > > -- > > "I say never be complete, I say stop being perfect, I say let... > > lets evolve, let the chips fall where they may." - Tyler Durden > > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
Chris > > > On 2/14/07, David Blevins <[EMAIL PROTECTED]> wrote: > On Feb 14, 2007, at 1:59 PM, Christopher Blythe wrote: > > > Dain and David... > > > > Took a swag at deploying Daytrader on Geronimo 2.0-M2... During > > deployment, it complained about the openejb-jar.xml file missing > > from the EJB module. I added the one you provided earlier in this > > chain, but for some reason it is still complaining that the openejb- > > jar.xml file is missing from the EJB module. I think Matt is > > probably running into the same issue... > > > > Does the or-mapping file also need to go in the ear/jar somewhere? > > Should this work on M2? Is there anything else that needs to go > > into the jar/ear? > > > > It really seems to me like we need way too many extra xml files to > > deploy this thing. > > You shouldn't need any files in the ear, i.e. passing the plan as a > parameter on the command line should work as always. > > Post the message text and a stack trace (if there is one) and I'll > see if I can't find what part of the code is confused. > > -David > > > > > Thanks... > > > > Chris > > > > > > > > > > > > On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:I just fix that > > allows nested openejb plans to work correctly. This > > was a big problem in the tck since all plans use the nested model. > > > > -dain > > > > On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > > > > > OK, I think the conversion tool should be full working now. > > > > > > There were loads of tiny bugs causing deployments to fail > > > especially around cmp. I tested the converter with the OpenEJB2 > > > itests which use almost every feature of OpenEJB2 and the > > > application now deploys with out error now. Of course there are > > > things sill unimplemented or ported to 3, so if you try to use > > > those features, you will get an exception at runtime. > > > > > > Let us know if you find any problems with the converter. > > > > > > -dain > > > > > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > > > > > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: > > >> > > >>> Haven't been able to get a full deploy of anything (tried > > >>> daytrader and the v2 itests), but things are starting to look > > >>> good with the converter. The basic conversion is happening and > > >>> conversion of things like environment and abstract name queries > > >>> are definitely getting ported over. Still see some hiccups in > > >>> CMPs, but apps without CMPs may deploy just fine. Will look > into > > >>> it more when I get up. > > >>> > > >>> Dain, can you take a look at the persistence unit part of the > > >>> rewritten EjbModuleBuilder. Seems something in the way i've > > >>> reworked the code results in those not coming through so well. > > >> > > >> Looking at it now. > > >> > > >> -dain > > >> > > > > > > > > > > > > > -- > > "I say never be complete, I say stop being perfect, I say let... > > lets evolve, let the chips fall where they may." - Tyler Durden > > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
eeds to go > into the jar/ear? > > It really seems to me like we need way too many extra xml files to > deploy this thing. You shouldn't need any files in the ear, i.e. passing the plan as a parameter on the command line should work as always. Post the message text and a stack trace (if there is one) and I'll see if I can't find what part of the code is confused. -David > > Thanks... > > Chris > > > > > > On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:I just fix that > allows nested openejb plans to work correctly. This > was a big problem in the tck since all plans use the nested model. > > -dain > > On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > > > OK, I think the conversion tool should be full working now. > > > > There were loads of tiny bugs causing deployments to fail > > especially around cmp. I tested the converter with the OpenEJB2 > > itests which use almost every feature of OpenEJB2 and the > > application now deploys with out error now. Of course there are > > things sill unimplemented or ported to 3, so if you try to use > > those features, you will get an exception at runtime. > > > > Let us know if you find any problems with the converter. > > > > -dain > > > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > > > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: > >> > >>> Haven't been able to get a full deploy of anything (tried > >>> daytrader and the v2 itests), but things are starting to look > >>> good with the converter. The basic conversion is happening and > >>> conversion of things like environment and abstract name queries > >>> are definitely getting ported over. Still see some hiccups in > >>> CMPs, but apps without CMPs may deploy just fine. Will look into > >>> it more when I get up. > >>> > >>> Dain, can you take a look at the persistence unit part of the > >>> rewritten EjbModuleBuilder. Seems something in the way i've > >>> reworked the code results in those not coming through so well. > >> > >> Looking at it now. > >> > >> -dain > >> > > > > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
e... > > > > Does the or-mapping file also need to go in the ear/jar somewhere? > > Should this work on M2? Is there anything else that needs to go > > into the jar/ear? > > > > It really seems to me like we need way too many extra xml files to > > deploy this thing. > > You shouldn't need any files in the ear, i.e. passing the plan as a > parameter on the command line should work as always. > > Post the message text and a stack trace (if there is one) and I'll > see if I can't find what part of the code is confused. > > -David > > > > > Thanks... > > > > Chris > > > > > > > > > > > > On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:I just fix that > > allows nested openejb plans to work correctly. This > > was a big problem in the tck since all plans use the nested model. > > > > -dain > > > > On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > > > > > OK, I think the conversion tool should be full working now. > > > > > > There were loads of tiny bugs causing deployments to fail > > > especially around cmp. I tested the converter with the OpenEJB2 > > > itests which use almost every feature of OpenEJB2 and the > > > application now deploys with out error now. Of course there are > > > things sill unimplemented or ported to 3, so if you try to use > > > those features, you will get an exception at runtime. > > > > > > Let us know if you find any problems with the converter. > > > > > > -dain > > > > > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > > > > > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: > > >> > > >>> Haven't been able to get a full deploy of anything (tried > > >>> daytrader and the v2 itests), but things are starting to look > > >>> good with the converter. The basic conversion is happening and > > >>> conversion of things like environment and abstract name queries > > >>> are definitely getting ported over. Still see some hiccups in > > >>> CMPs, but apps without CMPs may deploy just fine. Will look into > > >>> it more when I get up. > > >>> > > >>> Dain, can you take a look at the persistence unit part of the > > >>> rewritten EjbModuleBuilder. Seems something in the way i've > > >>> reworked the code results in those not coming through so well. > > >> > > >> Looking at it now. > > >> > > >> -dain > > >> > > > > > > > > > > > > > -- > > "I say never be complete, I say stop being perfect, I say let... > > lets evolve, let the chips fall where they may." - Tyler Durden > > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
x that > allows nested openejb plans to work correctly. This > was a big problem in the tck since all plans use the nested model. > > -dain > > On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > > > OK, I think the conversion tool should be full working now. > > > > There were loads of tiny bugs causing deployments to fail > > especially around cmp. I tested the converter with the OpenEJB2 > > itests which use almost every feature of OpenEJB2 and the > > application now deploys with out error now. Of course there are > > things sill unimplemented or ported to 3, so if you try to use > > those features, you will get an exception at runtime. > > > > Let us know if you find any problems with the converter. > > > > -dain > > > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > > > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: > >> > >>> Haven't been able to get a full deploy of anything (tried > >>> daytrader and the v2 itests), but things are starting to look > >>> good with the converter. The basic conversion is happening and > >>> conversion of things like environment and abstract name queries > >>> are definitely getting ported over. Still see some hiccups in > >>> CMPs, but apps without CMPs may deploy just fine. Will look into > >>> it more when I get up. > >>> > >>> Dain, can you take a look at the persistence unit part of the > >>> rewritten EjbModuleBuilder. Seems something in the way i've > >>> reworked the code results in those not coming through so well. > >> > >> Looking at it now. > >> > >> -dain > >> > > > > > > > -- > "I say never be complete, I say stop being perfect, I say let... > lets evolve, let the chips fall where they may." - Tyler Durden -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
On Feb 14, 2007, at 1:59 PM, Christopher Blythe wrote: Dain and David... Took a swag at deploying Daytrader on Geronimo 2.0-M2... During deployment, it complained about the openejb-jar.xml file missing from the EJB module. I added the one you provided earlier in this chain, but for some reason it is still complaining that the openejb- jar.xml file is missing from the EJB module. I think Matt is probably running into the same issue... Does the or-mapping file also need to go in the ear/jar somewhere? Should this work on M2? Is there anything else that needs to go into the jar/ear? It really seems to me like we need way too many extra xml files to deploy this thing. You shouldn't need any files in the ear, i.e. passing the plan as a parameter on the command line should work as always. Post the message text and a stack trace (if there is one) and I'll see if I can't find what part of the code is confused. -David Thanks... Chris On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote:I just fix that allows nested openejb plans to work correctly. This was a big problem in the tck since all plans use the nested model. -dain On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > OK, I think the conversion tool should be full working now. > > There were loads of tiny bugs causing deployments to fail > especially around cmp. I tested the converter with the OpenEJB2 > itests which use almost every feature of OpenEJB2 and the > application now deploys with out error now. Of course there are > things sill unimplemented or ported to 3, so if you try to use > those features, you will get an exception at runtime. > > Let us know if you find any problems with the converter. > > -dain > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: >> >>> Haven't been able to get a full deploy of anything (tried >>> daytrader and the v2 itests), but things are starting to look >>> good with the converter. The basic conversion is happening and >>> conversion of things like environment and abstract name queries >>> are definitely getting ported over. Still see some hiccups in >>> CMPs, but apps without CMPs may deploy just fine. Will look into >>> it more when I get up. >>> >>> Dain, can you take a look at the persistence unit part of the >>> rewritten EjbModuleBuilder. Seems something in the way i've >>> reworked the code results in those not coming through so well. >> >> Looking at it now. >> >> -dain >> > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: Conversion Tool
Dain and David... Took a swag at deploying Daytrader on Geronimo 2.0-M2... During deployment, it complained about the openejb-jar.xml file missing from the EJB module. I added the one you provided earlier in this chain, but for some reason it is still complaining that the openejb-jar.xml file is missing from the EJB module. I think Matt is probably running into the same issue... Does the or-mapping file also need to go in the ear/jar somewhere? Should this work on M2? Is there anything else that needs to go into the jar/ear? It really seems to me like we need way too many extra xml files to deploy this thing. Thanks... Chris On 2/7/07, Dain Sundstrom <[EMAIL PROTECTED]> wrote: I just fix that allows nested openejb plans to work correctly. This was a big problem in the tck since all plans use the nested model. -dain On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: > OK, I think the conversion tool should be full working now. > > There were loads of tiny bugs causing deployments to fail > especially around cmp. I tested the converter with the OpenEJB2 > itests which use almost every feature of OpenEJB2 and the > application now deploys with out error now. Of course there are > things sill unimplemented or ported to 3, so if you try to use > those features, you will get an exception at runtime. > > Let us know if you find any problems with the converter. > > -dain > > On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: > >> On Feb 6, 2007, at 6:37 AM, David Blevins wrote: >> >>> Haven't been able to get a full deploy of anything (tried >>> daytrader and the v2 itests), but things are starting to look >>> good with the converter. The basic conversion is happening and >>> conversion of things like environment and abstract name queries >>> are definitely getting ported over. Still see some hiccups in >>> CMPs, but apps without CMPs may deploy just fine. Will look into >>> it more when I get up. >>> >>> Dain, can you take a look at the persistence unit part of the >>> rewritten EjbModuleBuilder. Seems something in the way i've >>> reworked the code results in those not coming through so well. >> >> Looking at it now. >> >> -dain >> > -- "I say never be complete, I say stop being perfect, I say let... lets evolve, let the chips fall where they may." - Tyler Durden
Re: [VOTE] J2G Conversion tool acceptance
Hi Paul, We're in the process of getting the codebase cleaned up, refactored, and adding maven support. However, I will need your assistance with the ip-clearance form. Thanks. -Jeff On 2/8/07, Paul McMahan <[EMAIL PROTECTED]> wrote: IIUC we're at step 3 of this process right now -- contributor replaces copyright statements with the standard apache header. Adding maven support and changing the package names from com.ibm.* to org.apache.* would be very useful as well if that's possible. I can help with step 4 - submitting the ip clearance form and checking in to geronimo/sandbox. Once in sandbox we should discuss how/when it can be updated to support geronimo 1.2 & 2.0 and merged with the devtools subproject. Best wishes, Paul On 2/1/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: > Here's the process : > > 1) Contributor offers code > > 2) Project decides to accept or reject code. Formally, this is the > PMC, but everyone should chime in. > > 3) Contributor provides CCLA, cleans up code to remove copyright > statements, and puts the standard apache file header in place. > > 4) Project accepts code contribution and registers the code > contribution w/ the incubator with an ip_clearance form : > > http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ > ip-clearance/ > > 5) Happy users convert their JBoss apps to Geronimo. > > There's no need for the creation of a podling for accepting code into > an existing project, unless you wanted to bring in people and create > a community around it. We simply need to file an ip-clearance form > w/ the incubator that notes that we did the due diligence in > accepting the code. > > geir > > > > On Jan 31, 2007, at 10:10 AM, Filip Hanik - Dev Lists wrote: > > > This is the formal vote to accept the J2G codebase and bring it > > through incubation (see http://marc.theaimsgroup.com/?l=geronimo- > > dev&m=116906208022256&w=2) > > The final destination is to be part of the geronimo devtool > > subproject. > > (see http://marc.theaimsgroup.com/?l=geronimo- > > dev&m=116958894929809&w=2) > > > > The code donation is located at: > > https://issues.apache.org/jira/browse/GERONIMO-2743 > > > > [ ] +1 lets bring it in, this is great > > [ ] 0 do what ever you want, not my cup of tea > > [ ] -1 keep it out of our sight, I have a good reason > > > > Optional > > [ ] I'm willing to mentor this project while it is in incubation > > [ ] I'm willing to champion the effort while it is in incubation > > > > Committers' votes are binding, all other votes will be duly noted > > > > Best regards > > Filip > >
Re: [VOTE] J2G Conversion tool acceptance
IIUC we're at step 3 of this process right now -- contributor replaces copyright statements with the standard apache header. Adding maven support and changing the package names from com.ibm.* to org.apache.* would be very useful as well if that's possible. I can help with step 4 - submitting the ip clearance form and checking in to geronimo/sandbox. Once in sandbox we should discuss how/when it can be updated to support geronimo 1.2 & 2.0 and merged with the devtools subproject. Best wishes, Paul On 2/1/07, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote: Here's the process : 1) Contributor offers code 2) Project decides to accept or reject code. Formally, this is the PMC, but everyone should chime in. 3) Contributor provides CCLA, cleans up code to remove copyright statements, and puts the standard apache file header in place. 4) Project accepts code contribution and registers the code contribution w/ the incubator with an ip_clearance form : http://svn.apache.org/viewvc/incubator/public/trunk/site-author/ ip-clearance/ 5) Happy users convert their JBoss apps to Geronimo. There's no need for the creation of a podling for accepting code into an existing project, unless you wanted to bring in people and create a community around it. We simply need to file an ip-clearance form w/ the incubator that notes that we did the due diligence in accepting the code. geir On Jan 31, 2007, at 10:10 AM, Filip Hanik - Dev Lists wrote: > This is the formal vote to accept the J2G codebase and bring it > through incubation (see http://marc.theaimsgroup.com/?l=geronimo- > dev&m=116906208022256&w=2) > The final destination is to be part of the geronimo devtool > subproject. > (see http://marc.theaimsgroup.com/?l=geronimo- > dev&m=116958894929809&w=2) > > The code donation is located at: > https://issues.apache.org/jira/browse/GERONIMO-2743 > > [ ] +1 lets bring it in, this is great > [ ] 0 do what ever you want, not my cup of tea > [ ] -1 keep it out of our sight, I have a good reason > > Optional > [ ] I'm willing to mentor this project while it is in incubation > [ ] I'm willing to champion the effort while it is in incubation > > Committers' votes are binding, all other votes will be duly noted > > Best regards > Filip
Re: Conversion Tool
I just fix that allows nested openejb plans to work correctly. This was a big problem in the tck since all plans use the nested model. -dain On Feb 6, 2007, at 9:10 PM, Dain Sundstrom wrote: OK, I think the conversion tool should be full working now. There were loads of tiny bugs causing deployments to fail especially around cmp. I tested the converter with the OpenEJB2 itests which use almost every feature of OpenEJB2 and the application now deploys with out error now. Of course there are things sill unimplemented or ported to 3, so if you try to use those features, you will get an exception at runtime. Let us know if you find any problems with the converter. -dain On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: On Feb 6, 2007, at 6:37 AM, David Blevins wrote: Haven't been able to get a full deploy of anything (tried daytrader and the v2 itests), but things are starting to look good with the converter. The basic conversion is happening and conversion of things like environment and abstract name queries are definitely getting ported over. Still see some hiccups in CMPs, but apps without CMPs may deploy just fine. Will look into it more when I get up. Dain, can you take a look at the persistence unit part of the rewritten EjbModuleBuilder. Seems something in the way i've reworked the code results in those not coming through so well. Looking at it now. -dain
Re: Conversion Tool
OK, I think the conversion tool should be full working now. There were loads of tiny bugs causing deployments to fail especially around cmp. I tested the converter with the OpenEJB2 itests which use almost every feature of OpenEJB2 and the application now deploys with out error now. Of course there are things sill unimplemented or ported to 3, so if you try to use those features, you will get an exception at runtime. Let us know if you find any problems with the converter. -dain On Feb 6, 2007, at 9:57 AM, Dain Sundstrom wrote: On Feb 6, 2007, at 6:37 AM, David Blevins wrote: Haven't been able to get a full deploy of anything (tried daytrader and the v2 itests), but things are starting to look good with the converter. The basic conversion is happening and conversion of things like environment and abstract name queries are definitely getting ported over. Still see some hiccups in CMPs, but apps without CMPs may deploy just fine. Will look into it more when I get up. Dain, can you take a look at the persistence unit part of the rewritten EjbModuleBuilder. Seems something in the way i've reworked the code results in those not coming through so well. Looking at it now. -dain
Re: Conversion Tool
On Feb 6, 2007, at 6:37 AM, David Blevins wrote: Haven't been able to get a full deploy of anything (tried daytrader and the v2 itests), but things are starting to look good with the converter. The basic conversion is happening and conversion of things like environment and abstract name queries are definitely getting ported over. Still see some hiccups in CMPs, but apps without CMPs may deploy just fine. Will look into it more when I get up. Dain, can you take a look at the persistence unit part of the rewritten EjbModuleBuilder. Seems something in the way i've reworked the code results in those not coming through so well. Looking at it now. -dain
Re: Conversion Tool
Haven't been able to get a full deploy of anything (tried daytrader and the v2 itests), but things are starting to look good with the converter. The basic conversion is happening and conversion of things like environment and abstract name queries are definitely getting ported over. Still see some hiccups in CMPs, but apps without CMPs may deploy just fine. Will look into it more when I get up. Dain, can you take a look at the persistence unit part of the rewritten EjbModuleBuilder. Seems something in the way i've reworked the code results in those not coming through so well. -David On Jan 31, 2007, at 11:05 PM, David Blevins wrote: Reposting this info with more details. So the 10,000 foot perspective is that we are creating a conversion tool to convert the prior openejb-jar.xml into the new set of descriptors (geronimo-openejb.xml, new openejb-jar.xml, jpa entity- mappings.xml). It is expected that all existing plans will work and no one will have to or even *should* migrate just yet. We are doing this for two reasons: 1. There is significant investment in current descriptor format. These come to mind: - TCK - DayTrader - iTests - Samples - All documentation to date - All user-land apps to date 2. The new plans will not be stable for a good long while. Primary reasons are: - Continued work in integration (security, webservices, corba, etc.) - Continued work implementing JavaEE 5 So the big motivation for the conversion tool is that with some hard work from Dain and I up front (and for a while really), we can save a few hundred developer and user hours over the next couple months. We're very close to having something running and hope to see something basically working by the end of the week. If we're really lucky after this week we can hide all the change under the conversion tool and no one (but the people working on and maintaining the conversion tool that is) will have to feel the pain or frustration while things move underneath. As we enable things like security people won't have to update their plans, we'll just add more conversion logic to port that information over and put it into action. I can say that the spirit of the new descriptor files is to fully embrace the "anti-descriptor" focus of Java EE 5 and to be as small and contain as little requirements as possible. Hopefully when the day comes to move over (not soon), it will more be a matter of deleting than adding. There will definitely be lots of experimentation in that area, so we'll see. As always, thoughts and questions very welcome and encouraged. -David On Jan 31, 2007, at 3:13 PM, Dain Sundstrom wrote: I just checked in the working converter for CMP beans. There is a fairly extensive test suite that converts the OpenEJB2 itests, daytrader and the OpenEJB2 CMR mappings tests. For example, here are the mappings for daytrader ejb-jar.xml --- https://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3/ container/openejb-core/src/test/resources/convert/oej2/cmp/ daytrader/daytrader-ejb-jar.xml openejb-jar.xml --- https://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3/ container/openejb-core/src/test/resources/convert/oej2/cmp/ daytrader/daytrader-openejb-jar.xml And the final JPA mappings -- https://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb3/ container/openejb-core/src/test/resources/convert/oej2/cmp/ daytrader/daytrader-orm.xml I hope to have the converter fully integrated into Geronimo in by the end of the week. -dain On Jan 21, 2007, at 11:01 PM, David Blevins wrote: On Jan 19, 2007, at 5:07 PM, David Blevins wrote: Keep your ejb related plan files intact or a copy of them at least. I'm going to try and write a conversion tool that will at least handle trivial apps. A non-trivial app would be one with CMPs. The new mapping.xml format for cmps is the jpa mapping.xml and converting that will be a little more work. Nothing done yet, just announcing intentions. Ok, have a little progress on this. So far I am able to convert: - and children - and children - and children - and children - and children To see same converted document, look here: source: http://svn.apache.org/repos/asf/incubator/openejb/trunk/ openejb3/container/openejb-jee/src/test/resources/openejb-jar-2- full.xml result: http://svn.apache.org/repos/asf/incubator/openejb/trunk/ openejb3/container/openejb-jee/src/test/resources/geronimo- openejb-converted.xml It was a bit of work getting JAXB2 to work with our schemas because of duplicated elements combined with the fact that we allow invalid xml (i.e. no namespace at all). So I actually had to write a invalid 2 valid xml converter before I could get started on the openejb-j
Re: [VOTE] J2G Conversion tool acceptance
On Feb 1, 2007, at 8:53 AM, Jim Jagielski wrote: On Jan 31, 2007, at 12:54 PM, Kevan Miller wrote: Filip, OK. Now I'm confused. Do you want Geronimo to accept a code donation? Or do you want to start a new project in incubator? I thought it was the former (and I'm pretty sure you do, too). The process IIUC is roughly 1. Geronimo votes to accept the donation 2. The Geronimo project fills out some paperwork (update an html page and fill out the IP Clearance form -- http:// incubator.apache.org/ip-clearance/ip-clearance-template.html) 3. The Incubator PMC is notified of the donation and given 48 hours to raise any objections. The Incubator is always involved for any large, existing, external codebase, even if it is simply to check the IP clearance issues. This is Filip's intent, afaik. In which case there's no mentoring needed. The PMC needs to fill out the form accurately, as in doing so, they will be reminded of (and record the status of) all significant IP-related issues in accepting the contribution. geir
Re: [VOTE] J2G Conversion tool acceptance
Hi, It's already tallied, but just for the record. [X] +1 lets bring it in, this is great [X] I'm willing to mentor this project while it is in incubation Jacek On 1/31/07, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: This is the formal vote to accept the J2G codebase and bring it through incubation (see http://marc.theaimsgroup.com/?l=geronimo-dev&m=116906208022256&w=2) The final destination is to be part of the geronimo devtool subproject. (see http://marc.theaimsgroup.com/?l=geronimo-dev&m=116958894929809&w=2) The code donation is located at: https://issues.apache.org/jira/browse/GERONIMO-2743 [ ] +1 lets bring it in, this is great [ ] 0 do what ever you want, not my cup of tea [ ] -1 keep it out of our sight, I have a good reason Optional [ ] I'm willing to mentor this project while it is in incubation [ ] I'm willing to champion the effort while it is in incubation Committers' votes are binding, all other votes will be duly noted Best regards Filip -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: [RESULT] VOTE J2G Conversion tool acceptance
Filip, let me know if you need anything fro me. Thanks for spearheading this. On Feb 2, 2007, at 10:01 AM, Filip Hanik - Dev Lists wrote: Here is the result: +1; Jeff Genender Paul McMahan Kevan Miller Prasad Kashyap Hernan Cunico Dain Sundstrom David Jencks Cris Cardona Aaron Mulder David Blevins Anita Kulshreshtha Gianny Damour Rick McGuire Matt Hogstrom Sachin Patel Vamsi Reddy No 0's and no -1's. We will start filling out the IP clearance form, and attach it to the JIRA item along with the updated codebase. We will use this template http://incubator.apache.org/ip-clearance/ip-clearance-template.html Once this has been done, we will bring the JIRA to the attention of the G committers for review. Filip Filip Hanik - Dev Lists wrote: This is the formal vote to accept the J2G codebase and bring it through incubation (see http://marc.theaimsgroup.com/?l=geronimo- dev&m=116906208022256&w=2) The final destination is to be part of the geronimo devtool subproject. (see http://marc.theaimsgroup.com/?l=geronimo- dev&m=116958894929809&w=2) The code donation is located at: https://issues.apache.org/jira/browse/GERONIMO-2743 [ ] +1 lets bring it in, this is great [ ] 0 do what ever you want, not my cup of tea [ ] -1 keep it out of our sight, I have a good reason Optional [ ] I'm willing to mentor this project while it is in incubation [ ] I'm willing to champion the effort while it is in incubation Committers' votes are binding, all other votes will be duly noted Best regards Filip
