This is our first official non incubating release, yeah! :-)
Congrats Freeman for the good job as a release manager.
On 9/25/07, Freeman Fang [EMAIL PROTECTED] wrote:
The Apache ServiceMix team is proud to announce the availability of
the 3.1.2 release!
Apache ServiceMix is a TLP (Top Level
Thanks Guillaume. :-)
Freeman
Guillaume Nodet wrote:
This is our first official non incubating release, yeah! :-)
Congrats Freeman for the good job as a release manager.
On 9/25/07, Freeman Fang [EMAIL PROTECTED] wrote:
The Apache ServiceMix team is proud to announce the availability of
Btw, will you add a news item in the front page of the web site ?
Just click the Add news link on the top right when you are in confluence.
On 9/25/07, Guillaume Nodet [EMAIL PROTECTED] wrote:
This is our first official non incubating release, yeah! :-)
Congrats Freeman for the good job as a
I will update the release guide.
I add one
* we need download maven-stage-plugin and build it ourselves if we want
to run mvn stage:copy since this plugin isn't published.
Cheers
Freeman
Guillaume Nodet wrote:
I think we should add a section to the release guide with all the
checks we need
Done.
http://cwiki.apache.org/confluence/display/SM/2007/09/25/ServiceMix+3.1.2+released
Just waiting for it show up in the front page.
Cheers
Freeman
Guillaume Nodet wrote:
Btw, will you add a news item in the front page of the web site ?
Just click the Add news link on the top right when
I've taken a first stab at adding an easy way of integration testing
JBI artifacts (shared libraries, components and service assemblies)
using a simple Spring XML notation that can be included into any JUnit
test case...
http://cwiki.apache.org/SM/integration-testing-in-spring.html
This allows
Hello,
First of all congratulations for being graduated as a top level proyecto at
the ASF. It's was about time considering all the efforts the whole group has
done for this piece of fine work.
I dont know if I should post a jira about this issue I found following the
Apache Servicemix Tutorial.
Now that servicemix has graduated, the repository has changed.
ServiceMix is not deployed to the incubating repository anymore but to
the official repository which is mirror to the public ones. 3.1.2 has
just been released, so you may need some time before all the mirrors
are uptodate, but it
Hi,
Are there any concrete plans considering such functionality? I've seen
something written on WS-Policy What is the current status of this ? The
thing is that sometimes we need trivial functionality
like catch exchange before processing (to log or do metrics). Sometimes it
could be nice to
Hi,
Since srevicemic 3.1.2 is released after graduate, so now you should find
3.1.2 artifacts from
http://people.apache.org/repo/m2-ibiblio-rsync-repository
Would you please add this url to your maven settings.xml, this should
resolve your build problem.
Best Regards
Freeman
Eduardo de Vera
gnodet wrote:
What kind of use case do you have exactly ?
Listeners are not enough I think since it is based only on events. What
about around interceptors and eg. situation when you want to cancel some
exchange? My case is standard one. We have to proxy eg. jms bc (in fact it
is
The code in the geronimo-acivation server module should be moved into the
javamail provider package
---
Key: GERONIMO-3485
URL:
[
https://issues.apache.org/jira/browse/GERONIMO-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530087
]
Rick McGuire commented on GERONIMO-3485:
Stage one complete, the addition of the handlers to the javamail
Were these changes also included in the 2.0 branch for 2.0.2?
The JIRA only mentions 2.1 trunk and there is no Subversion Commits history,
but the Fix For field says it was fixed for 2.0x and 2.1.
-Donald
David Blevins (JIRA) wrote:
[
Hi,
As Guillaume point out, our release to
http://people.apache.org/repo/m2-ibiblio-rsync-repository already
synchronized by http://repo1.maven.org/maven2/org/apache/servicemix now, so
it's unnecessary to change your maven settings.xml and I believe you can
build successfully.
Cheers
Freeman
[
https://issues.apache.org/jira/browse/GERONIMO-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3484.
--
Resolution: Fixed
Fixed in 2.0.2 (branches/2.0 and openejb 3.0-beta-1) openejb rev 579080
I've committed to branches/2.0 also.
thanks
david jencks
On Sep 25, 2007, at 1:47 AM, David Jencks wrote:
On Sep 24, 2007, at 8:52 AM, Anita Kulshreshtha wrote:
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Sep 20, 2007, at 8:38 AM, Donald Woods wrote:
I see that Anita has attached
I just tried and it tried to install into my local maven repo
(?!?!?!) and I have to go get on a plane. Until this is straightened
out building g. 2.0.2-SNAPSHOT will require building openejb locally
first.
thanks
david jencks
ServiceMix 4.0 is a big change compared to ServiceMix 3.x.
We will still support JBI 1.0 of course, but we will leverage OSGi has
much as possible. This means that the deployment unit will be mostly
an OSGi bundle (instead of SU / SA).
One of the building block of ServiceMix is also Camel which
[
https://issues.apache.org/jira/browse/DAYTRADER-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher James Blythe closed DAYTRADER-53.
-
Resolution: Fixed
Fix Version/s: 2.0
Assignee:
Missing logic in EJB mode to detect holdings that have already been sold
Key: DAYTRADER-55
URL: https://issues.apache.org/jira/browse/DAYTRADER-55
Project: DayTrader
[
https://issues.apache.org/jira/browse/DAYTRADER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher James Blythe closed DAYTRADER-24.
-
Resolution: Fixed
Clean up plan files in 1.2 branch
[
https://issues.apache.org/jira/browse/DAYTRADER-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher James Blythe closed DAYTRADER-54.
-
Resolution: Fixed
Fix Version/s: 2.0
1.2
[
https://issues.apache.org/jira/browse/GERONIMO-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy reopened GERONIMO-3484:
---
Does not seem to solve the problem on branches\2.0. Openejb config is
But this kind of feature can not easily be generic. It would be
specific for each kind of endpoints I suppose. Just to understand
your use case a bit more, what do you want to do with messages that
you don't want to process ? Just discard them ? Then you could use a
filter (and use the route
[
https://issues.apache.org/jira/browse/GERONIMO-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy closed GERONIMO-3484.
-
Resolution: Fixed
Changed the dependency scope to runtime. Revision: 579289
David, I tried both the local and xa rars for oracle and it works good
with daytrader (without any issue in G2188). I have a question on the
local and xa rars. Is there any reason why we want to continue
releasing the local rars? Seems it is rather confusing to have so many
rars for a
On Tuesday 25 September 2007, Guillaume Nodet wrote:
I think we should add a section to the release guide with all the
checks we need to do to verify the release:
* artifacts are signed
* KEYS file present with key inside
* check this bug of the gpg plugin
This one will be gone soon.
gnodet wrote:
But this kind of feature can not easily be generic. It would be
specific for each kind of endpoints I suppose. Just to understand
your use case a bit more, what do you want to do with messages that
you don't want to process ? Just discard them ? Then you could use a
Actually, within 4 hours of upload, it should be at central and within a
day from there, out to all the mirrors.Thus, you shouldn't need to
add anything to the poms now.Yea!!
Dan
On Tuesday 25 September 2007, Freeman Fang wrote:
Hi,
Since srevicemic 3.1.2 is released after
It would be nice to use that and do some functional test / load
testing using the soap ui maven plugin too...
On 9/25/07, James Strachan [EMAIL PROTECTED] wrote:
I've taken a first stab at adding an easy way of integration testing
JBI artifacts (shared libraries, components and service
--- David Jencks [EMAIL PROTECTED] wrote:
On Sep 20, 2007, at 8:56 AM, Anita Kulshreshtha wrote:
I am leaning towards deploying MEJB as an EJBModule. To auto
deploy
this I will be adding an mejb config. Are there any objections?
no :-)
I've been wondering if we should try to
On 9/25/07, Jacek Laskowski [EMAIL PROTECTED] wrote:
On 9/25/07, David Jencks [EMAIL PROTECTED] wrote:
I just tried and it tried to install into my local maven repo
(?!?!?!) and I have to go get on a plane. Until this is straightened
out building g. 2.0.2-SNAPSHOT will require building
On Sep 24, 2007, at 3:03 PM, David Jencks wrote:
On Sep 20, 2007, at 8:56 AM, Anita Kulshreshtha wrote:
I am leaning towards deploying MEJB as an EJBModule. To auto
deploy
this I will be adding an mejb config. Are there any objections?
no :-)
I've been wondering if we should try to
On Sep 25, 2007, at 8:51 AM, David Jencks wrote:
I've committed to branches/2.0 also.
Thanks David!
I think this leaves us with:
* integration of the MEJB code itself
* release of OpenEJB 3.0-Beta
One thing I've noticed -- the default JNDI name for EJB's has been
changed in OpenEJB. So,
[
https://issues.apache.org/jira/browse/GERONIMO-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530145
]
Vamsavardhana Reddy commented on GERONIMO-3481:
---
GERONIMO-3484 is resolved. But then
On 9/25/07, Przemyslaw Budzik [EMAIL PROTECTED] wrote:
gnodet wrote:
But this kind of feature can not easily be generic. It would be
specific for each kind of endpoints I suppose. Just to understand
your use case a bit more, what do you want to do with messages that
you don't want
Vamsi,
In general I think we agree on how things should be handled when
schema changes. Also, the patch I looked at had schema changes made in
the existing .xsd files and I assumed that the new files would be
introduced in trunk only. But since nobody else has an issue with that
change, that's
On 9/25/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
Wait. Why is 2.0.2-SNAPSHOT dependent on 3.0-beta-1?!
https://issues.apache.org/jira/browse/GERONIMO-3484
Well, I think it should be fixed with using the recent openejb 3.0.0-SNAPSHOT.
Jacek
--
Jacek Laskowski
[
https://issues.apache.org/jira/browse/GERONIMO-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3452:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
[
https://issues.apache.org/jira/browse/GERONIMO-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3437:
---
Affects Version/s: 2.0.x
Fix Version/s: 2.0.2
Added Fixed For 2.0.2, so we can
[
https://issues.apache.org/jira/browse/GERONIMO-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3420:
---
Fix Version/s: (was: 2.0.x)
2.0.2
Added Fixed For 2.0.2, so we can
[
https://issues.apache.org/jira/browse/GERONIMO-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3405:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
2.1
[
https://issues.apache.org/jira/browse/GERONIMO-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3421:
---
Fix Version/s: (was: 2.0.x)
2.0.2
Added Fixed For 2.0.2, so we can
[
https://issues.apache.org/jira/browse/GERONIMO-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3391:
---
Fix Version/s: (was: 2.0.x)
2.0.2
Updated Fixed For field
Use
[
https://issues.apache.org/jira/browse/GERONIMO-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3400:
---
Fix Version/s: (was: 2.0.x)
2.0.1
Updated Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3390:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
Server
[
https://issues.apache.org/jira/browse/GERONIMO-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3388:
---
Fix Version/s: (was: 2.0.x)
2.0.1
LoginKerberosTest relies on
[
https://issues.apache.org/jira/browse/GERONIMO-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3388:
---
Fix Version/s: (was: 2.0.1)
2.0.2
updated Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3383:
---
Description:
Under LDAP portlet, after input Host localhost,port 10389 and User DN,
[
https://issues.apache.org/jira/browse/GERONIMO-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3386:
---
Fix Version/s: (was: 2.0.x)
2.1
2.0.2
updated
[
https://issues.apache.org/jira/browse/GERONIMO-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3378:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3376:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
can't
[
https://issues.apache.org/jira/browse/GERONIMO-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3380:
---
Affects Version/s: 2.0.x
Fix Version/s: 2.0.2
updated Fixed For field, as the
[
https://issues.apache.org/jira/browse/GERONIMO-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3329:
---
Fix Version/s: (was: 2.0)
2.0.2
update Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3374:
---
Affects Version/s: 2.1
Fix Version/s: 2.1
updated Fixed For field
Admin console
[
https://issues.apache.org/jira/browse/GERONIMO-3317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3317:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
has
[
https://issues.apache.org/jira/browse/GERONIMO-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2851:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
LDAP
[
https://issues.apache.org/jira/browse/GERONIMO-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3324:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
Could
[
https://issues.apache.org/jira/browse/GERONIMO-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-1746:
---
Affects Version/s: 2.1
2.0
Fix Version/s: (was: 2.0.x)
Agree.
-Donald
Lin Sun wrote:
David, I tried both the local and xa rars for oracle and it works good
with daytrader (without any issue in G2188). I have a question on the
local and xa rars. Is there any reason why we want to continue
releasing the local rars? Seems it is rather
Sounds good. +1
-Donald
Rick McGuire wrote:
I ran into a situation where somebody wishing to use the Geronimo
javamail implementation also need to extract the geroinimo-activation
jar file from the server assembly. This was needed because the various
activation datahandlers are not
[
https://issues.apache.org/jira/browse/GERONIMO-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3467:
---
Affects Version/s: 2.1
Fix Version/s: 2.1
Confusing security exception thrown
BTW - I'm going through JIRA today and updating any Fix For: 2.0.x
closed/resolved issues to use the correct release attribute, so we can
generate a valid list of fixes for the 2.0.2 release notes
-Donald
Kevan Miller wrote:
All,
I think it's time to start rolling out a 2.0.2 release.
[
https://issues.apache.org/jira/browse/GERONIMO-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3459:
---
Affects Version/s: (was: 2.0.x)
Fix Version/s: (was: 2.0.x)
updated Fixed
[
https://issues.apache.org/jira/browse/GERONIMO-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3439:
---
Affects Version/s: (was: 2.0.x)
2.0
[
https://issues.apache.org/jira/browse/GERONIMO-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3404:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
[
https://issues.apache.org/jira/browse/GERONIMO-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3410:
---
Fix Version/s: (was: 2.0.x)
2.0.1
jspc-maven-plugin-2.0-alpha-1
[
https://issues.apache.org/jira/browse/GERONIMO-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3426:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
[
https://issues.apache.org/jira/browse/GERONIMO-3414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3414:
---
Affects Version/s: 2.1
2.0.1
Fix Version/s: (was:
[
https://issues.apache.org/jira/browse/GERONIMO-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3435:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
Hi All,
trying to deal with the schemas update on the web site and I'm looking to some
things I would like to get your input.
First of all the actual schemas file name don't match the target name space
defined in the schema itself.
Here is the associated JIRA (
[
https://issues.apache.org/jira/browse/GERONIMO-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3411:
---
Affects Version/s: 2.1
Fix Version/s: (was: 2.0.x)
[
https://issues.apache.org/jira/browse/GERONIMO-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2025:
---
Affects Version/s: 2.1
2.0.x
updated affects field
Undeploy and
[
https://issues.apache.org/jira/browse/GERONIMO-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2025:
---
Fix Version/s: (was: 2.0.x)
2.1
2.0.2
Undeploy
[
https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2964:
---
Fix Version/s: (was: 2.0.x)
Cannot specify the Tomcat work directory for a web
[
https://issues.apache.org/jira/browse/GERONIMO-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods closed GERONIMO-3363.
--
Resolution: Fixed
Fix Version/s: (was: 2.0.x)
2.1
[
https://issues.apache.org/jira/browse/GERONIMO-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-895:
--
Fix Version/s: (was: 2.0.x)
updated Fixed For field
Remove JAAS login's reliance on
[
https://issues.apache.org/jira/browse/GERONIMO-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3387:
---
Fix Version/s: (was: 2.0.x)
2.0.1
2.1
updated
[
https://issues.apache.org/jira/browse/GERONIMO-3385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3385:
---
Fix Version/s: (was: 2.0.x)
2.0.1
updated Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2286:
---
Fix Version/s: (was: 2.0.x)
updated Fixed For field
app client plan still uses
[
https://issues.apache.org/jira/browse/GERONIMO-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3406:
---
Fix Version/s: (was: 2.0)
(was: 2.0.x)
2.0.1
[
https://issues.apache.org/jira/browse/GERONIMO-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3407:
---
Fix Version/s: (was: 2.0)
(was: 2.0.x)
2.0.1
[
https://issues.apache.org/jira/browse/GERONIMO-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3401:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
Stop
[
https://issues.apache.org/jira/browse/GERONIMO-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-2567:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
Remote
[
https://issues.apache.org/jira/browse/GERONIMO-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3360:
---
Fix Version/s: (was: 2.0.x)
2.0
2.0.1
On 9/19/07, David Blevins [EMAIL PROTECTED] wrote:
On Sep 18, 2007, at 7:07 AM, Hernan Cunico wrote:
I talked with Dave Blevins about this, maybe I got it wrong. Dave
can you take a look at this?
We should still use the same schema from G 1.2 for now. There's a
lot of documentation for
Nope, but sounds like a good job for the maven-release-plugin :-)
-Donald
Hernan Cunico wrote:
Hi All,
trying to deal with the schemas update on the web site and I'm looking
to some things I would like to get your input.
First of all the actual schemas file name don't match the target
would this plugin be smart enough to place/rename the schemas in the right
directory accordingly to what's specified as the target name space?
Cheers!
Hernan
Donald Woods wrote:
Nope, but sounds like a good job for the maven-release-plugin :-)
-Donald
Hernan Cunico wrote:
Hi All,
[
https://issues.apache.org/jira/browse/GERONIMO-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530249
]
Donald Woods commented on GERONIMO-3423:
Was this also fixed in the 2.0 branch (aka. 2.0.2) ???
There is
[
https://issues.apache.org/jira/browse/GERONIMO-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3240:
---
Fix Version/s: (was: 2.0.x)
2.0.1
updated Fixed For field
Unable
[
https://issues.apache.org/jira/browse/GERONIMO-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3348:
---
Fix Version/s: (was: 2.0.x)
2.1
2.0.2
updated
[
https://issues.apache.org/jira/browse/GERONIMO-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3409:
---
Fix Version/s: (was: 2.0.x)
2.0.1
2.0.2
updated
[
https://issues.apache.org/jira/browse/GERONIMO-3310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3310:
---
Fix Version/s: (was: 2.0.x)
2.1
2.0.2
updated
[
https://issues.apache.org/jira/browse/GERONIMO-3248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3248:
---
Fix Version/s: (was: 2.0.x)
updated Fixed For field
Extraneous WARN messages during
[
https://issues.apache.org/jira/browse/GERONIMO-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3412:
---
Fix Version/s: (was: 2.0.x)
2.0.2
updated Fixed For field
[
https://issues.apache.org/jira/browse/GERONIMO-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated GERONIMO-3471:
---
Fix Version/s: (was: 2.0.x)
(was: 2.1)
updated Fixed For field
I'm not that big a fan of trying to make the schema namespace be an
actual working URL. Should the schema's namespace end in .xsd?
That seems weird. Plus we have no control over the location for many
of the schemas we use (other projects we use, the Sun schemas, etc.)
And it might result in us
I was being smart a$$... :-)
It doesn't handle schemas today, nor does maven-deploy-plugin
-Donald
Hernan Cunico wrote:
would this plugin be smart enough to place/rename the schemas in the
right directory accordingly to what's specified as the target name space?
Cheers!
Hernan
Donald
OK, I'm done updating the 2.0.x closed issues (sorry for all the JIRA emails.)
The only one I couldn't figure out, was:
https://issues.apache.org/jira/browse/GERONIMO-3423
-Donald
Donald Woods wrote:
BTW - I'm going through JIRA today and updating any Fix For: 2.0.x
1 - 100 of 121 matches
Mail list logo