Menu
▾
▴
maven-plugins-developer — Mailing List used for development of plugins
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(14) |
Oct
(1) |
Nov
|
Dec
(1) |
| 2004 |
Jan
(4) |
Feb
(8) |
Mar
(14) |
Apr
(18) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(1) |
Sep
(5) |
Oct
(26) |
Nov
(36) |
Dec
(21) |
| 2005 |
Jan
(10) |
Feb
(20) |
Mar
(15) |
Apr
(11) |
May
(29) |
Jun
(18) |
Jul
(19) |
Aug
(12) |
Sep
(11) |
Oct
(3) |
Nov
(7) |
Dec
(5) |
| 2006 |
Jan
(7) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(14) |
Jul
(45) |
Aug
(58) |
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2007 |
Jan
(4) |
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jeff J. <jef...@up...> - 2006-07-31 15:09:37
|
=20 > -----Original Message----- > From: mav...@li...=20 > [mailto:mav...@li...] > On Behalf Of J=F6rg Schaible > Sent: Monday, July 31, 2006 8:25 AM > To: mav...@li... > Subject: Re: [Maven-plugins-developer] [Maven-plugins-user]=20 > Publishedjavaapp-1.4-snapshot >=20 > Hi Jeff, >=20 > Jeff Jensen wrote on Monday, July 31, 2006 2:57 PM: >=20 > > Hi J=F6rg, > >=20 > > Eclipse files: Because other plugins have the Eclipse=20 > files, they are=20 > > source-config files, and I found it convenient when they=20 > were already=20 > > there so I added them to the projects I setup to fix things on. >=20 > Since you generate them normally with Maven anyway, I find it=20 > normally quite scary, if I have suddenly conflicts updating a=20 > project. Especially if it includes settings that may not=20 > match my preferences ;-) >=20 > But it might be a mood point for javaapp, since meanwhile I=20 > switched to M2 also any my motivation to maintain M1 plugins=20 > has been . That's a good point. I don't use the maven eclipse plugin, so that = would be why! :-) With the various projects I work on, and my customers' work, = we always source-control the IDE config files too. So it is also a habit! No one else has been working on these SF plugins for about a year, so I = also didn't expect anyone to care! :-) If they are bothersome, we can consider deleting them. > > Version num: Because I just bumped the rev since I'm not sure what=20 > > else is going into the releases yet. I have been applying some=20 > > patches and trying to fix some issues to eliminate the ancient=20 > > backlog! If others such as yourself will take the plugin version=20 > > numbers quite seriously, then I will do the sub-point=20 > release approach=20 > > in the future. >=20 > I released 1.3.1 also from 1.4-SNAPSHOT. As long as it just=20 > contains bug fixes without any new functionality or=20 > incompatible changes, it might be the better approach. Certainly. Will respect that traditional approach again. It was also = part of the "I didn't expect anyone to care". ;-) > > Keeping track of added issues: Recently I changed all SF=20 > trackers to=20 > > email changes to the dev list. This will make it easier=20 > for us to see=20 > > them vs continually polling. >=20 > Fine. That always annoyed me. I catched some entries=20 > regarding javaapp, but I had to admin that I did not check=20 > the entries in the last months ... so thanks for taking up=20 > the torch :) For a few plugins that I have particularly maintained, there were 2 = defects logged at the beginning of July, and I just found them the other day. I passionately hate that kind of poor response! I had configured the = maillist sending before that, but for some reason not all emails made it through. They seem to come through correctly now though. Not sure what changed. Thanks for your input/concerns/replies. Nice to know others will = monitor and care about these still! Even though you have moved on to M2, any expertise you can provide on applying any of the patches in the Patches and/or Bugs trackers would be very helpful. Some of them I can't process easily/quickly due to lack = of understanding the plugin (I have not used most of these!), so they = become longer to process and slower for me to get to. And I hesitate as well, = as I would rather not break something more!=20 |
|
From: <Joe...@El...> - 2006-07-31 13:25:23
|
Hi Jeff, Jeff Jensen wrote on Monday, July 31, 2006 2:57 PM: > Hi J=F6rg, >=20 > Eclipse files: Because other plugins have the Eclipse files, they are > source-config files, and I found it convenient when they were already > there so I added them to the projects I setup to fix things on. Since you generate them normally with Maven anyway, I find it normally = quite scary, if I have suddenly conflicts updating a project. Especially = if it includes settings that may not match my preferences ;-) But it might be a mood point for javaapp, since meanwhile I switched to = M2 also any my motivation to maintain M1 plugins has been . > Version num: Because I just bumped the rev since I'm not sure > what else is > going into the releases yet. I have been applying some > patches and trying > to fix some issues to eliminate the ancient backlog! If > others such as > yourself will take the plugin version numbers quite > seriously, then I will > do the sub-point release approach in the future. I released 1.3.1 also from 1.4-SNAPSHOT. As long as it just contains bug = fixes without any new functionality or incompatible changes, it might be = the better approach. > Keeping track of added issues: Recently I changed all SF > trackers to email > changes to the dev list. This will make it easier for us to > see them vs > continually polling. Fine. That always annoyed me. I catched some entries regarding javaapp, = but I had to admin that I did not check the entries in the last months = ... so thanks for taking up the torch :) - J=F6rg |
|
From: Jeff J. <jef...@up...> - 2006-07-31 12:57:21
|
See other thread. =20 -----Original Message----- From: mav...@li... [mailto:mav...@li...] On Behalf = Of J=F6rg Schaible Sent: Monday, July 31, 2006 1:59 AM To: Jeff Jensen; mav...@li... Subject: Re: [Maven-plugins-developer] [Maven-plugins-user] Publishedjavaapp-1.4-snapshot Hi Jeff, Jeff Jensen wrote on Sunday, July 30, 2006 5:47 AM: > Hi, >=20 > I just deployed a 1.4-snapshot release of the javaapp plugin. The=20 > only change is for issue 1436490 "EJB jars are not bundled" [1] with=20 > fix by Daniel Schulz (Thanks Daniel!). >=20 >=20 > Please test and report results on that issue. >=20 >=20 > [1] > = http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1436490&grou= p > _id=3D61626&atid=3D497853 Can you tell me, why you've added suddenly Eclipse project files to the repo? And - since it is a simple bug fix - make a 1.3.2 release ... - J=F6rg ... who wonders ever, how one should keep track of the added issues at = SF ... ;-) -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join = SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Maven-plugins-developer mailing list Mav...@li... https://lists.sourceforge.net/lists/listinfo/maven-plugins-developer |
|
From: Jeff J. <jef...@up...> - 2006-07-31 12:57:16
|
Hi J=F6rg, Eclipse files: Because other plugins have the Eclipse files, they are source-config files, and I found it convenient when they were already = there so I added them to the projects I setup to fix things on. Version num: Because I just bumped the rev since I'm not sure what else = is going into the releases yet. I have been applying some patches and = trying to fix some issues to eliminate the ancient backlog! If others such as yourself will take the plugin version numbers quite seriously, then I = will do the sub-point release approach in the future. Keeping track of added issues: Recently I changed all SF trackers to = email changes to the dev list. This will make it easier for us to see them vs continually polling. -----Original Message----- From: J=F6rg Schaible [mailto:Joe...@El...]=20 Sent: Monday, July 31, 2006 1:59 AM To: Jeff Jensen; mav...@li... Subject: RE: [Maven-plugins-user] Published javaapp-1.4-snapshot Hi Jeff, Jeff Jensen wrote on Sunday, July 30, 2006 5:47 AM: > Hi, >=20 > I just deployed a 1.4-snapshot release of the javaapp plugin. The=20 > only change is for issue 1436490 "EJB jars are not bundled" [1] with=20 > fix by Daniel Schulz (Thanks Daniel!). >=20 >=20 > Please test and report results on that issue. >=20 >=20 > [1] > = http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1436490&grou= p > _id=3D61626&atid=3D497853 Can you tell me, why you've added suddenly Eclipse project files to the repo? And - since it is a simple bug fix - make a 1.3.2 release ... - J=F6rg ... who wonders ever, how one should keep track of the added issues at = SF ... ;-) |
|
From: <Joe...@El...> - 2006-07-31 06:58:58
|
Hi Jeff, Jeff Jensen wrote on Sunday, July 30, 2006 5:47 AM: > Hi, >=20 > I just deployed a 1.4-snapshot release of the javaapp plugin. The > only change is for issue 1436490 "EJB jars are not bundled" [1] with > fix by Daniel Schulz (Thanks Daniel!). >=20 >=20 > Please test and report results on that issue. >=20 >=20 > [1] > = http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1436490&grou= p_id=3D61626&atid=3D497853 Can you tell me, why you've added suddenly Eclipse project files to the = repo? And - since it is a simple bug fix - make a 1.3.2 release ... - J=F6rg ... who wonders ever, how one should keep track of the added issues at = SF ... ;-) |
|
From: SourceForge.net <no...@so...> - 2006-07-31 06:51:52
|
Bugs item #1515768, was opened at 2006-07-02 08:14 Message generated for change (Comment added) made by wdsgoe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1515768&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: webtest Group: None Status: Pending Resolution: None Priority: 9 Submitted By: Krystian Nowak (krystian_nowak) Assigned to: Siegfried GOESCHL (wdsgoe) Summary: [webtest] needs 2.0 to work with dojo Initial Comment: Since webtest plugin in version 1.2 doesn't work with applications using dojo (http://dojotoolkit.org/) I had to upgrade dependencies in the plugin to canoo webtest 2.0 which works with dojo. Home-made version (1.3-RC-1) of the plugin is waiting to be reviewed by webtest plugin developers, but I couldn't attached it - I guess due to the file size. How can I do it? Kind regards, Krystian Nowak ---------------------------------------------------------------------- >Comment By: Siegfried GOESCHL (wdsgoe) Date: 2006-07-31 06:51 Message: Logged In: YES user_id=183881 Hi folks, since I'm out of the maven-plugins loop ... +) I created a local version of the Maven Canoo WebTest plugin which is a bad thing to start with ... :-( +) Are the patches you are talking about already under CVS - if yes then I only have to merge my changes with the CVS head revision +) I will release the plugin on Wednesday ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 03:04 Message: Logged In: YES user_id=498804 Thanks, I appreciate you tracking that down! I do not use the plugin, so will rely on your/actual users help to ensure it works correctly to your satisfaction. ---------------------------------------------------------------------- Comment By: Krystian Nowak (krystian_nowak) Date: 2006-07-29 19:09 Message: Logged In: YES user_id=1294218 Right now I guess only Siegfried Goeschl can generate diff files, since my fix was totally unaware of changes in current version of the plugin. Siegfried has it and I hope he can help you. I will try to notify him about it. Regards, Krystian ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 19:03 Message: Logged In: YES user_id=498804 Would still like the diffs or the entire changed files to apply, if you will provide only the changed files. ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-27 14:51 Message: Logged In: YES user_id=498804 If someone wants it applied to the source here, attach patch(es) and I will gladly apply and release snapshots until we get it to work. ---------------------------------------------------------------------- Comment By: Krystian Nowak (krystian_nowak) Date: 2006-07-27 14:05 Message: Logged In: YES user_id=1294218 It's already done here http://people.apache.org/~sgoeschl/ by Siegfried Goeschl ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-27 03:47 Message: Logged In: YES user_id=498804 Don't attach entire plugin, attach only patches of changed files. Are the only changes the POM dependencies? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1515768&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-31 02:12:00
|
Bugs item #1247702, was opened at 2005-07-29 17:15 Message generated for change (Comment added) made by brill You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1247702&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: axis Group: None Status: Pending Resolution: None Priority: 5 Submitted By: Peter Monks (pmonks) Assigned to: Jeff Jensen (jeffjensen) Summary: [axis] Axis Plugin unable to read WSDL file from URL Initial Comment: The Maven Axis plugin v0.7 appears to be unable to read a WSDL file from a URL (eg. http://www.4s4c.com/wsdl/demo.wsdl), even though Axis itself (the command line wsdl2java tool) is able to read WSDL files from a URL just fine. If a URL is specified in the maven.axis.url property, the following message appears in the build output: axis:prepare-filesystem: Not invoking Axis plugin ---------------------------------------------------------------------- Comment By: Brill Pappin (brill) Date: 2006-07-30 22:11 Message: Logged In: YES user_id=7933 Sorry... I've moved on to Maven 2. I did have some workaround but it's been so long that I can't tell you what is was that I did, and don't have access to the project anymore. ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:15 Message: Logged In: YES user_id=498804 I know it has been awhile, but do either of you have a precise suggested change to fix? Either paste the existing lines and the precise changes to make here, or attach a patch if it gets more than simple... I don't use this plugin, so would prefer expert user guidance instead of trying various things myself (which would take a lot longer!). ---------------------------------------------------------------------- Comment By: Brill Pappin (brill) Date: 2005-08-09 13:00 Message: Logged In: YES user_id=7933 Same problem here... the plugin.jelly script has a check for an existing file, which of cources failes is the file is a remote WSDL and no a local file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1247702&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:58:19
|
Patches item #971151, was opened at 2004-06-11 09:16 Message generated for change (Settings changed) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971151&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: jaxb Group: None Status: Pending Resolution: None Priority: 5 Submitted By: Guillaume Lasnier (guette) Assigned to: Jeff Jensen (jeffjensen) >Summary: [jaxb] added flexibility to gen or artifacts Initial Comment: This patch adds more flexibility to the generation of jaxb artifacts by exposing some attributes of the xjc task. It enables : using external binding files choosing the target output directory provide additionnal command line arguments ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:56 Message: Logged In: YES user_id=498804 Hi Guillaume, Please do same with this one if you are still interested. I would like to fix these for you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971151&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:56:59
|
Patches item #971151, was opened at 2004-06-11 09:16 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971151&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: jaxb Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Guillaume Lasnier (guette) >Assigned to: Jeff Jensen (jeffjensen) Summary: Maven jaxb plugin added flexibility Initial Comment: This patch adds more flexibility to the generation of jaxb artifacts by exposing some attributes of the xjc task. It enables : using external binding files choosing the target output directory provide additionnal command line arguments ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:56 Message: Logged In: YES user_id=498804 Hi Guillaume, Please do same with this one if you are still interested. I would like to fix these for you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971151&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:55:49
|
Patches item #971130, was opened at 2004-06-11 08:49 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971130&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: jaxb Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Guillaume Lasnier (guette) >Assigned to: Jeff Jensen (jeffjensen) >Summary: [jaxb] project.xml patch for dependencies Initial Comment: This patch defines precisly the depedencies that are needed to compile and run JAXB application. The dependencies are those provided the JWSDP 1.3 release. ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:55 Message: Logged In: YES user_id=498804 Hi Guillaume, It is a shame your patches have been unapplied for 2 years. I am trying to catchup all the issues and patches. If you are still interested, please resubmit your patches from latest, as it looks like the files have changed since you created the patches and I am unsure of what to apply due to my unfamiliarity with it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=971130&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:48:26
|
Patches item #1200499, was opened at 2005-05-12 05:25 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=1200499&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: jaxb Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Ted (tedsanne) >Assigned to: Jeff Jensen (jeffjensen) Summary: [jaxb] support for DTDs Initial Comment: This improvements to the maven-jaxb-plugin contains the following: - The root classloader is removed - Jars have been removed from plugin-resources and configured as dependencies instead - Support for DTDs These changes have been made by Havard Bjastad of TraceTracker. ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:48 Message: Logged In: YES user_id=498804 Hi Ted, if you are still interested, would you mind creating patches for the files from latest instead of providing all of them as a whole? I would like to add this for you, and the patch approach will be faster and easier for me to use. I think there has been some other file changes since the files in your attached zip. ---------------------------------------------------------------------- Comment By: Ted (tedsanne) Date: 2005-09-05 03:35 Message: Logged In: YES user_id=1277243 I have checked out version 1.1.0 of the plugin, but it still does not support DTDs ---------------------------------------------------------------------- Comment By: Pat (mavenj) Date: 2005-06-06 00:05 Message: Logged In: YES user_id=1290338 line 51 (plugin.jelly): the test for dtds is done inside the test for xsd. I think this test should be done after the xsd test, so that both xsd and dtds can have their own block of xjc execution. I'd love for support for DTDs to be available in this plugin very soon! - mavenj ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=1200499&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:23:05
|
Bugs item #1336145, was opened at 2005-10-24 03:54 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1336145&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: jaxb Group: release >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Jeff Jensen (jeffjensen) Summary: [jaxb] does not use dependency classpath Initial Comment: When using the JAXB plugin with MAVEN 1.0.2, the project dependencies classpath is ignored. This is because the plugin.jelly is incorrect. It says : <xjc extension="${maven.jaxb.extension}" package="${maven.jaxb.package}" target="${maven.jaxb.build.dir}"> <schema dir="${maven.jaxb.src.dir}" includes="${maven.jaxb.schema.includes}" excludes="${maven.jaxb.schema.excludes}"/> <binding dir="${maven.jaxb.src.dir}" includes="${maven.jaxb.bindings.includes}" excludes="${maven.jaxb.bindings.excludes}"/> <ant:classpath> <ant:pathelement path="${maven.build.dest}" /> <ant:pathelement path="${maven.dependency.classpath}" /> </ant:classpath> </xjc> While in fact, the classpath should use a refid like so : <ant:path refid="maven.dependency.classpath" /> ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:23 Message: Logged In: YES user_id=498804 Sorry - just found your patch on the patches list. Thanks a bunch for doing that. It is applied and I will release a snapshot for it. ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 16:12 Message: Logged In: YES user_id=498804 Are you saying to replace this: <ant:classpath> <ant:pathelement path="${maven.build.dest}" /> <ant:pathelement path="${maven.dependency.classpath}" /> </ant:classpath> with this: <ant:path refid="maven.dependency.classpath" /> ? If not, please clarify precisely the change you are recommending, or even better please attach a patch! ---------------------------------------------------------------------- Comment By: Brice C. (brice_c) Date: 2005-10-24 03:55 Message: Logged In: YES user_id=65157 submitted by SF user brice_c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1336145&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:22:11
|
Patches item #1336156, was opened at 2005-10-24 04:09 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=1336156&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: jaxb Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Brice C. (brice_c) >Assigned to: Jeff Jensen (jeffjensen) Summary: [jaxb] Proper use of maven dependency classpath for XJC Initial Comment: This is a patch for bug 1336145 previously reported by me. Please apply ASAP if proven to work in maven 1.1 - otherwise the JAXB plugin misses a key functionality ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:22 Message: Logged In: YES user_id=498804 Patch applied, thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497855&aid=1336156&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:10:06
|
Bugs item #1104628, was opened at 2005-01-18 11:14 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1104628&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: axis Group: release >Status: Pending Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Jeff Jensen (jeffjensen) Summary: maven-axis-plugin single url (external) wsdl2java bug. Initial Comment: the jelly script detects single urls wrongfully. It might be me, since I'm fairly new to this, but there is no way it seems to generate the java stubs for a remote webservice on a remote host. The current way its written it triggers for single generation when the url property ends with .wsdl, hard to submit a remote url then :) Proposed patch is to detect if start of url starts with http ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:10 Message: Logged In: YES user_id=498804 Hi, I'd like to fix this for you and release a snapshot. Do you have a precise change(s) or patch to attach? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-01-18 11:16 Message: Logged In: NO Or even better patch... edit the wsdlPostfix property to have "wsdl" instead of ".wsdl" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1104628&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 22:05:23
|
Bugs item #1229554, was opened at 2005-06-29 03:55 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1229554&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: weblogic Group: release >Status: Pending Resolution: None Priority: 5 Submitted By: Andreas Schönknecht (schoolm) >Assigned to: Jeff Jensen (jeffjensen) Summary: [weblogic] weblogic:redeploy has missing parameter Initial Comment: Hi, I tried the weblogic:redeploy goal and got an error message telling that the "-source" must be provided when "-upload" is used. I use weblogic server 8.1.3. [java] java.lang.IllegalArgumentException: When the - upload option is specified, the -source option must also be specified. [java] at weblogic.Deployer.runBodyWithAuthenticatedSubject (Deployer.java:827) [java] at weblogic.Deployer.runBody (Deployer.java:711) [java] at weblogic.utils.compiler.Tool.run (Tool.java:146) [java] at weblogic.utils.compiler.Tool.run (Tool.java:103) [java] at weblogic.Deployer.runMain (Deployer.java:566) [java] When the -upload option is specified, the -source option must also be specified. [java] at weblogic.Deployer.main(Deployer.java:549) [java] [java] [java] Usage: java weblogic.Deployer [options] [actions] [File(s)] [java] [java] where options include: [java] -adminurl <<protocol>://<server>:<port>> Administration server URL: [java] default iiop://localhost:7001 [java] -username <username> user name [java] -password <password> password for the user [java] -userconfigfile <userconfigfile> The user config file contains the [java] user security credentials; it is [java] administered by the weblogic.Admin tool [java] -userkeyfile <keyConfigFile> The users key file; it is administered [java] by the weblogic.Admin tool. [java] -examples Displays example usage of this tool. [java] -name <application name> Defaults to the basename of the deployment [java] file or directory. [java] -targets <<target(s)>> A comma separated list of targets for the [java] current operation. If not specified, all [java] configured targets are used. For a new [java] application, the default target is the [java] administration server. [java] -deploy Make an application available for service. [java] -redeploy Replace a running application partially or [java] entirely. [java] -undeploy Take an application out of service. [java] ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 17:05 Message: Logged In: YES user_id=498804 Hi, Could you attach a patch for a fix? Did you ever fix this for yourself locally? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1229554&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 21:32:23
|
Bugs item #1115849, was opened at 2005-02-03 17:50 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1115849&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: dbunit Group: None >Status: Pending >Resolution: Fixed Priority: 5 Submitted By: Stephen Cooper (scooper) >Assigned to: Jeff Jensen (jeffjensen) Summary: [dbunit] Set autocommit to true Initial Comment: Not all JDBC drivers have autocommit = true as the default. DBUnit seems to require this. I'll be posting a similar bug to dbunit, but for now the most expedient solution for my problem is to patch maven-dbunit-plugin. Here's the diff: cvs diff src/main/net/sourceforge/mavenplugins/dbunit/DbUnitTool.java Index: src/main/net/sourceforge/mavenplugins/dbunit/DbUnitTool.java =================================================================== RCS file: /cvsroot/maven-plugins/maven-plugins/dbunit/src/main/net/sourceforge/mavenplugins/dbunit/DbUnitTool.java,v retrieving revision 1.3 diff -r1.3 DbUnitTool.java 152a153 > jdbcConnection.setAutoCommit(true); 218c219 < } \ No newline at end of file --- > } ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 16:32 Message: Logged In: YES user_id=498804 Thanks for reporting this (a long time ago! :-(. I have committed your change and published 1.8-snapshot. Please test and report your results here. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1115849&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 21:15:32
|
Bugs item #1247702, was opened at 2005-07-29 16:15 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1247702&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: axis Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Peter Monks (pmonks) >Assigned to: Jeff Jensen (jeffjensen) Summary: [axis] Axis Plugin unable to read WSDL file from URL Initial Comment: The Maven Axis plugin v0.7 appears to be unable to read a WSDL file from a URL (eg. http://www.4s4c.com/wsdl/demo.wsdl), even though Axis itself (the command line wsdl2java tool) is able to read WSDL files from a URL just fine. If a URL is specified in the maven.axis.url property, the following message appears in the build output: axis:prepare-filesystem: Not invoking Axis plugin ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 16:15 Message: Logged In: YES user_id=498804 I know it has been awhile, but do either of you have a precise suggested change to fix? Either paste the existing lines and the precise changes to make here, or attach a patch if it gets more than simple... I don't use this plugin, so would prefer expert user guidance instead of trying various things myself (which would take a lot longer!). ---------------------------------------------------------------------- Comment By: Brill Pappin (brill) Date: 2005-08-09 12:00 Message: Logged In: YES user_id=7933 Same problem here... the plugin.jelly script has a check for an existing file, which of cources failes is the file is a remote WSDL and no a local file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1247702&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 21:12:10
|
Bugs item #1336145, was opened at 2005-10-24 03:54 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1336145&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: jaxb Group: release >Status: Pending Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Jeff Jensen (jeffjensen) >Summary: [jaxb] does not use dependency classpath Initial Comment: When using the JAXB plugin with MAVEN 1.0.2, the project dependencies classpath is ignored. This is because the plugin.jelly is incorrect. It says : <xjc extension="${maven.jaxb.extension}" package="${maven.jaxb.package}" target="${maven.jaxb.build.dir}"> <schema dir="${maven.jaxb.src.dir}" includes="${maven.jaxb.schema.includes}" excludes="${maven.jaxb.schema.excludes}"/> <binding dir="${maven.jaxb.src.dir}" includes="${maven.jaxb.bindings.includes}" excludes="${maven.jaxb.bindings.excludes}"/> <ant:classpath> <ant:pathelement path="${maven.build.dest}" /> <ant:pathelement path="${maven.dependency.classpath}" /> </ant:classpath> </xjc> While in fact, the classpath should use a refid like so : <ant:path refid="maven.dependency.classpath" /> ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 16:12 Message: Logged In: YES user_id=498804 Are you saying to replace this: <ant:classpath> <ant:pathelement path="${maven.build.dest}" /> <ant:pathelement path="${maven.dependency.classpath}" /> </ant:classpath> with this: <ant:path refid="maven.dependency.classpath" /> ? If not, please clarify precisely the change you are recommending, or even better please attach a patch! ---------------------------------------------------------------------- Comment By: Brice C. (brice_c) Date: 2005-10-24 03:55 Message: Logged In: YES user_id=65157 submitted by SF user brice_c ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1336145&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 21:05:04
|
Bugs item #1363121, was opened at 2005-11-21 15:41 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1363121&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sourceforge Group: cvshead >Status: Pending Resolution: None Priority: 5 Submitted By: S (notzippy) Assigned to: Jeff Jensen (jeffjensen) Summary: [sourceforge] plugin broken because of new sf namespace Initial Comment: Hi The source forge plugin is broken because sf.net now declares a name space in the html. The fix is to register the name space and prefix each search with the name space. Like the following private static final String SOURCEFORGE_NAMESPACE = "http://www.w3.org/1999/xhtml"; context.registerNamespace("sf", SOURCEFORGE_NAMESPACE); context.getValue("//sf:font[text()='Invalid Password or User Name']"); ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-30 16:05 Message: Logged In: YES user_id=498804 I am unfamiliar and do not use this plugin, but would like to fix it for you. Can you point me to each location to make your suggested changes (e.g. on the invalid pw locations, or all context.getValue() locations?)? Better yet, could you make the changes and attach a patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1363121&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 20:49:30
|
Bugs item #1363121, was opened at 2005-11-21 15:41 Message generated for change (Settings changed) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1363121&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sourceforge Group: cvshead Status: Open Resolution: None Priority: 5 Submitted By: S (notzippy) >Assigned to: Jeff Jensen (jeffjensen) >Summary: [sourceforge] plugin broken because of new sf namespace Initial Comment: Hi The source forge plugin is broken because sf.net now declares a name space in the html. The fix is to register the name space and prefix each search with the name space. Like the following private static final String SOURCEFORGE_NAMESPACE = "http://www.w3.org/1999/xhtml"; context.registerNamespace("sf", SOURCEFORGE_NAMESPACE); context.getValue("//sf:font[text()='Invalid Password or User Name']"); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1363121&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 03:07:52
|
Bugs item #1370823, was opened at 2005-12-01 05:44 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1370823&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: sdocbook Group: release >Status: Pending Resolution: None Priority: 5 Submitted By: Jean-François El Fouly (jfelfouly) >Assigned to: Nobody/Anonymous (nobody) Summary: Images not included in generated PDF Initial Comment: While the setup seems correct and I have jimi 1.0 jar in my maven repository, I keep getting this error (while converting docbooks for the Scarab project): [java] [INFO] JAI support was not installed (read: not present at build time). Trying to use Jimi instead [java] Error creating background image: Error creating FopImage object (http://docbook.sourceforge.net/release/images/draft.p ng) : Jimi image library not available The build succeeds but I get PDF's without their images; HTML conversion works fine. ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 22:07 Message: Logged In: YES user_id=498804 I know it has been a number of months since you reported this, do you have any new info to report? E.g. does the problem still exist, or did you find the solution? I do not use this plugin, but will gladly help you to get it fixed if you can help diagnose. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1370823&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 03:04:50
|
Bugs item #1515768, was opened at 2006-07-02 03:14 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1515768&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: webtest Group: None >Status: Pending Resolution: None Priority: 9 Submitted By: Krystian Nowak (krystian_nowak) Assigned to: Siegfried GOESCHL (wdsgoe) Summary: [webtest] needs 2.0 to work with dojo Initial Comment: Since webtest plugin in version 1.2 doesn't work with applications using dojo (http://dojotoolkit.org/) I had to upgrade dependencies in the plugin to canoo webtest 2.0 which works with dojo. Home-made version (1.3-RC-1) of the plugin is waiting to be reviewed by webtest plugin developers, but I couldn't attached it - I guess due to the file size. How can I do it? Kind regards, Krystian Nowak ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 22:04 Message: Logged In: YES user_id=498804 Thanks, I appreciate you tracking that down! I do not use the plugin, so will rely on your/actual users help to ensure it works correctly to your satisfaction. ---------------------------------------------------------------------- Comment By: Krystian Nowak (krystian_nowak) Date: 2006-07-29 14:09 Message: Logged In: YES user_id=1294218 Right now I guess only Siegfried Goeschl can generate diff files, since my fix was totally unaware of changes in current version of the plugin. Siegfried has it and I hope he can help you. I will try to notify him about it. Regards, Krystian ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 14:03 Message: Logged In: YES user_id=498804 Would still like the diffs or the entire changed files to apply, if you will provide only the changed files. ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-27 09:51 Message: Logged In: YES user_id=498804 If someone wants it applied to the source here, attach patch(es) and I will gladly apply and release snapshots until we get it to work. ---------------------------------------------------------------------- Comment By: Krystian Nowak (krystian_nowak) Date: 2006-07-27 09:05 Message: Logged In: YES user_id=1294218 It's already done here http://people.apache.org/~sgoeschl/ by Siegfried Goeschl ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-26 22:47 Message: Logged In: YES user_id=498804 Don't attach entire plugin, attach only patches of changed files. Are the only changes the POM dependencies? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1515768&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 02:59:29
|
Bugs item #1387499, was opened at 2005-12-21 14:47 Message generated for change (Settings changed) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1387499&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: cobertura Group: release >Status: Pending Resolution: None Priority: 5 Submitted By: psylence (psylence) >Assigned to: Jeff Jensen (jeffjensen) Summary: Using aspectj maven plugin confuses cobertura plugin Initial Comment: When compiling sources with an overridden java:compile goal like so: <preGoal name="java:compile"> <attainGoal name="aspectj:compile"/> </preGoal> (as recommended from: http://maven.apache.org/maven-1.x/reference/plugins/aspectj/index.html The cobertura plugin compiles the source twice, once correctly, then instruments it. It then gets to the test:test goal, at which time it compiles the source again, and copies it over the already instrumented code. The result is 0 coverage. The JCoverage maven plugin handles this without issue. The major difference I can see is the following from the reporting goals of the two plugins: cobertura:report <goal name="cobertura:report"> .. snip .. <attainGoal name="cobertura:on"/> <attainGoal name="test:test"/> jcoverage:report-html <goal name="jcoverage:report-html" prereqs="jcoverage:on,test:test"> Apparently maven considers java:compile as having been run when jcoverage:on is ran as a prereq? Not sure, but moving the cobertura:on,test:test into a prereq for cobertura:report ends in an error. ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 21:59 Message: Logged In: YES user_id=498804 1. Which cobertura version is everyone using that exhibits this problem - is everyone on 1.2? 2. Does this problem occur with version 1.1.1 of the plugin? 3. With version 1.2, set maven.cobertura.datafile to basedir and try again, like this: maven.cobertura.datafile=${basedir}/cobertura.ser Please try 1.1.1 and the property change with 1.2 and reply with your results! ---------------------------------------------------------------------- Comment By: Krystian Nowak (krystian_nowak) Date: 2006-07-05 08:14 Message: Logged In: YES user_id=1294218 could be duplicated by bug [ 1517491 ] cobertura.ser does not exis (https://sourceforge.net/tracker/index.php?func=detail&aid=1517491&group_id=61626&atid=497853) ---------------------------------------------------------------------- Comment By: stephane bouchet (le_phan) Date: 2006-03-07 09:22 Message: Logged In: YES user_id=572945 hi, having the same issue. Using maven 1.1-beta2, jdk 1.5, aspectj-plugin 3.3 SNAPSHOT and cobertura 1.2 SNAPSHOT. I had all my reports to 0% modified the cobertura:report has mantionned ( add prereqs ) and everything worked. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1387499&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-30 02:49:32
|
Bugs item #1432911, was opened at 2006-02-16 08:35 Message generated for change (Settings changed) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1432911&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: cobertura Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: [cobertura] failure when using aspectJ or Jibx Initial Comment: cobertura 1.6 fails when project uses AspectJ or Jibx bytecode processors. Using cobertura 1.7 solves this issue. Please upgrade dependency ! ---------------------------------------------------------------------- Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-26 22:58 Message: Logged In: YES user_id=498804 Cobertura plugin 1.2 uses Cobertura 1.8. Does this fix your problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1432911&group_id=61626 |
|
From: SourceForge.net <no...@so...> - 2006-07-29 19:40:20
|
Bugs item #1436490, was opened at 2006-02-22 02:37 Message generated for change (Comment added) made by jeffjensen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1436490&group_id=61626 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: javaapp Group: None >Status: Pending >Resolution: Fixed Priority: 5 Submitted By: Daniel Schulz (d-schulz) >Assigned to: Jeff Jensen (jeffjensen) >Summary: [javaapp] ejb jars are not bundled Initial Comment: There is the snippet: <goal name="javaapp:support-uberjar-bundle" ... <j:if test="${dep.getProperty('uberjar.bundle')=='false' || dep.type !='jar'}"> ... <j:set var="excludes" value="${excludes},${dep.artifactId}"/> that prevents bundling of ejb dependencies. An ejb-dependecies artifact-type is ebj and its file type is jar. So the test should be: <j:if test="${dep.getProperty('uberjar.bundle')=='false' || !(dep.type =='jar' || dep.type=='ejb')}"> Thank you, Daniel ---------------------------------------------------------------------- >Comment By: Jeff Jensen (jeffjensen) Date: 2006-07-29 14:40 Message: Logged In: YES user_id=498804 Thanks for reporting this and providing the fix. Sorry for the delay. I will commit your fix and release a snapshot (1.4 snapshot). You will see the email on the user list within the next few days. Please test and report your results on this defect thread! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=497853&aid=1436490&group_id=61626 |
