est jars for j2ee-builder tests
>
>
> Key: GERONIMO-2716
> URL: https://issues.apache.org/jira/browse/GERONIMO-2716
> Project: Geronimo
> Issue Type: Improvement
> Securi
your new jee5 app to test the latest schemas and specs.
What say you ?
> Create javaee 5 test jars for j2ee-builder tests
>
>
> Key: GERONIMO-2716
> URL: https://issues.apache.org/jira/brows
[
https://issues.apache.org/jira/browse/GERONIMO-2716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anita Kulshreshtha closed GERONIMO-2716.
Resolution: Fixed
> Create javaee 5 test jars for j2ee-builder te
!
> Create javaee 5 test jars for j2ee-builder tests
>
>
> Key: GERONIMO-2716
> URL: https://issues.apache.org/jira/browse/GERONIMO-2716
> Project: Geronimo
> Issue Type: Improv
for the
jsp_2.1 spec dependencies. Maybe you are relying on it being defined at a
higher level.
> Create javaee 5 test jars for j2ee-builder tests
>
>
> Key: GERONIMO-2716
> URL: https://issues.
gt;
>
> Create ear, ejb-jar, rar, and war files for j2ee-builder tests that use
> javaee 5 schema. Use servlet 2.5 and jsp 2.1 specs for all wars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://
apply it because the
test-deployment-javaee_5/* files don't exist yet.. The patch tries to update
files in that dir.
I get the following when I try to apply the patch
http://rifers.org/paste/show/3222
> Create javaee 5 test jars for j2ee-build
.
> Create javaee 5 test jars for j2ee-builder tests
>
>
> Key: GERONIMO-2716
> URL: https://issues.apache.org/jira/browse/GERONIMO-2716
> Project: Geronimo
> Issue Type: Improvement
=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
Want to start your own business?
Learn how on Yahoo! Small Business.
http://smallbusiness.yahoo.com/r-index
> Create javaee 5 test jars for j2ee-builder te
l: public(Regular issues)
> Components: deployment
>Affects Versions: 2.0-M2
> Environment: All
>Reporter: Anita Kulshreshtha
> Assigned To: Anita Kulshreshtha
> Fix For: 2.0-M2
>
> Attachments: testsupport.diff
>
>
> Creat
Create javaee 5 test jars for j2ee-builder tests
Key: GERONIMO-2716
URL: https://issues.apache.org/jira/browse/GERONIMO-2716
Project: Geronimo
Issue Type: Improvement
Security Level
following the docs here;
http://maven.apache.org/plugins/maven-dependency-plugin/
introduction.html
changed to match what is in the other poms (org.codehaus.mojo) and
works fine.
2) The j2ee-builder tests use a 'naked' ear that has been stripped
of its geronimo-application.xml
.
We are already using 1.0 of the dependency plugin...
org.codehaus.mojo
dependency-maven-plugin
1.0
2) The j2ee-builder tests use a 'naked' ear that has been stripped
of its geronimo-applic
x27;t
follow the maven community that closely so I'm not sure.
2) The j2ee-builder tests use a 'naked' ear that has been stripped of
its geronimo-application.xml file. Easy enough to do with ant and we
can do it with maven as well I'm sure but I was hoping you'd have
some
13 PM, Jason Dillon wrote:
Hi Bill... I don't think that will work... since as soon as I move
them the build will start failing, as those bits are still needed
to run the geronimo-j2ee-builder tests.
I'm not really concerned about the paper trail that we get with
svn mv for the
soon as I move
them the build will start failing, as those bits are still needed
to run the geronimo-j2ee-builder tests.
I'm not really concerned about the paper trail that we get with svn
mv for these. I'd rather just svn add the new tree of modules,
delete the old bits and a
Hi Bill... I don't think that will work... since as soon as I move
them the build will start failing, as those bits are still needed to
run the geronimo-j2ee-builder tests.
I'm not really concerned about the paper trail that we get with svn
mv for these. I'd rather just
Hi Jason,
Yes I made some progress. Not quite done as I ran into a redeploy bug
that I spent a bit of time poking at over the weekend. I think the
thing to do is to get the test stuff moved over and then I'll
experiment more with the redeploy bug.
From past experience patches generated by
Hiya Bill... didya happen to make any progress on this?
--jason
On Aug 25, 2006, at 1:28 PM, Bill Dudney wrote:
Hi Jason,
I'd be happy to do this. Do you have a direction yet on the
movement of modules? This would probably best fit in something like
trunk/test-deployables/${module-name}
I think test-deployables is fine... stuff is going to start moving
out of modules, might as well start with this one.
We may re-organize modules into a few smaller trees, like support,
core, j2ee, plugins... or something... more to come on that later for
discussion.
But for this, it does
Hi Jason,
I'd be happy to do this. Do you have a direction yet on the movement
of modules? This would probably best fit in something like
trunk/test-deployables/${module-name}
Does that sit well, or would you rather me put it into modules? Then
you can move it around when you move everythi
I think it would be good to turn those mock test apps into a set of
real m2 modules that build the j2ee deployables, then j2ee-deployer
can depend on them and not have to hack up its build to generate
them... and then those mock apps could be reused outside of that
module too... say to tes
Hi David,
Agreed, externalized would be best. SVN diff produces such poor
patches though when there are directory moves involved that I
hesitate to attempt something like that. If its palatable I could
simply copy them and make a patch that adds the copies then someone
could delete them f
On a related note I've been creating a bunch of little m2 projects to
build apps to verify defects and their fixes. Usually you have to
look at the output to see if it passed. I've been attaching these
projects to the issues in question. I think we should consider
putting these in svn so
Hi All,
The tests in the j2ee-builder do not currently have valid deployment
descriptors. While that's ok for this module because of the mocked
out deployment bits I was hoping to use them in other tests. I have
most of the stuff fixed up but there are a few things that I don't
want to do
25 matches
Mail list logo
