jimma closed pull request #855: [CXF-8371]:initial/experimental jakarta ee9
support with eclipse transformer
URL: https://github.com/apache/cxf/pull/855
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go
jimma commented on PR #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-1220452882
Close this as it's outdated.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
reta commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-963504372
@ffang this is just piece of great news, thank you for helping @jimma !
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
ffang commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-963391917
Hi @reta , @jimma ,
Surprisingly, I noticed that in the jakarta jar after transform, the OSGi
headers by and large are also taken care by the eclipse transformer plugin(some
ffang edited a comment on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-962448894
Hi @jimma , @reta ,
Thanks for bringing up this discussion!
As my comment in the dev mailling list(Jakarta namespace and OSGI), I think
this PR can skip OSGi support
ffang commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-962448894
Hi @jimma , @reta ,
As my comment in the dev mailling list(Jakarta namespace and OSGI), I think
this PR can skip OSGi support for now.
Best Regards
Freeman
--
This is
reta commented on a change in pull request #855:
URL: https://github.com/apache/cxf/pull/855#discussion_r725165439
##
File path: ee9/src/main/resources/gav.map
##
@@ -0,0 +1 @@
+jakarta.xml.ws;jakarta.xml.ws-api;* = jakarta.xml.ws;jakarta.xml.ws-api;3.0.1
Review comment:
reta commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-938841408
@jimma thank you, regarding your questions:
> Another thing I am not sure is : to transform cxf artifacts, should we
have some subset of cxf artifacts to transform first instead of tr
jimma commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-938404858
> Thanks for doing this work @jimma , I think if we just scope it to
rewriting packages in binary, it should work. There are 3 concerns which I
would like to hear your opinion:
>
jimma commented on a change in pull request #855:
URL: https://github.com/apache/cxf/pull/855#discussion_r724746727
##
File path: ee9/src/main/resources/gav.map
##
@@ -0,0 +1 @@
+jakarta.xml.ws;jakarta.xml.ws-api;* = jakarta.xml.ws;jakarta.xml.ws-api;3.0.1
Review comment:
jimma commented on a change in pull request #855:
URL: https://github.com/apache/cxf/pull/855#discussion_r724744247
##
File path: ee9/pom.xml
##
@@ -0,0 +1,1046 @@
+
+
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLoca
reta commented on pull request #855:
URL: https://github.com/apache/cxf/pull/855#issuecomment-935117118
Thanks for doing this work @jimma , I think if we just scope it to rewriting
packages in binary, it should work. There are 3 concerns which I would like to
hear your opinion:
- Rewri
reta commented on a change in pull request #855:
URL: https://github.com/apache/cxf/pull/855#discussion_r722786701
##
File path: ee9/src/main/resources/gav.map
##
@@ -0,0 +1 @@
+jakarta.xml.ws;jakarta.xml.ws-api;* = jakarta.xml.ws;jakarta.xml.ws-api;3.0.1
Review comment:
reta commented on a change in pull request #855:
URL: https://github.com/apache/cxf/pull/855#discussion_r722786016
##
File path: ee9/pom.xml
##
@@ -0,0 +1,1046 @@
+
+
+
+http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocat
Dev List
Subject: Re: Can't run SpnegoTokenTest in eclipse due to
javax.xml.ws.soap.SOAPFaultException:
net.sf.ehcache.Element.(Ljava/lang/Object;Ljava/lang/Object;II)V
It runs fine for me in eclipse. The error message looks like there is an
incorrect version of EhCache on the classpath.
It runs fine for me in eclipse. The error message looks like there is an
incorrect version of EhCache on the classpath.
Colm.
On Mon, Oct 15, 2018 at 9:01 PM wrote:
> Hi all,
>
>
>
> I am new to the CXF workspace.
>
>
>
> I have built and imported CXF into Eclips
Hi all,
I am new to the CXF workspace.
I have built and imported CXF into Eclipse on my own branch based on 3.2.6
I am attempting to run Junit test
org.apache.cxf.systest.kerberos.wssec.spnego.SpnegoTokenTest inside eclipse.
Upon doing so I get an error message:
Oct 15, 2018
e:
>>
>> This is an automated email from the ASF dual-hosted git repository.
>>
>> dkulp pushed a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/cxf-build-utils.git
>>
>>
>> The following commit(s) were added to
h master
> in repository https://gitbox.apache.org/repos/asf/cxf-build-utils.git
>
>
> The following commit(s) were added to refs/heads/master by this push:
> new eb8bcd9 Updates to checkstyle rules to support checkstyle 8.x which
> is now used in eclips
d rules and config. The updated buildutils also has updated
PMD rules. I’m kind of waiting on a “release” of buildutils as I ended up
submitting a bunch of pull requests to the pmd-eclipse plugin and I’m waiting
for a release of that which will even have an even newer version of PMD (also
not
Hi Daniel,
How did you go with getting cxf to support the latest checkstyle? Are we
still limited to older than 6.2?
On Sat, Feb 7, 2015 at 8:09 AM, Daniel Kulp wrote:
> Just a warning to the CXF devs: don’t update your eclipse plugin for
> check style. The new version i
Just a warning to the CXF devs: don’t update your eclipse plugin for check
style. The new version is very incompatible with our settings. What’s worse,
I cannot get it to be compatible with settings used with the
maven-eclipse-plugin (even the latest one released yesterday). I’m trying to
d to select a directory for
> the import,
> do you select checkout/cxf or checkout/cxf/distirubtion or
> checkout/cxf/distribution/target?
>
> Thanks,
> Ronnie
>
> On Wed, Nov 19, 2014 at 10:54 AM, Christian Schneider <
> ch...@die-schneider.net> wrote:
>
> >
014 at 10:54 AM, Christian Schneider <
ch...@die-schneider.net> wrote:
> I personally clone cxf into checkout/cxf.
>
> I start eclipse and use Import -> Existing maven project.
> Then I select either a single project or the top level one.
>
> After clicking though the wiza
I personally clone cxf into checkout/cxf.
I start eclipse and use Import -> Existing maven project.
Then I select either a single project or the top level one.
After clicking though the wizard the cxf moduls are imported nicely.
Christian
On 19.11.2014 04:05, RU(Ronnie) QUAN wrote:
Hi everyone,
I'm new to the group, want to clarify following instructions from
http://cxf.apache.org/setting-up-eclipse.html
Create the project in Eclipse
- In eclipse, switch to the workspace you created above.
- Go To:
File -> Import
- Select "Existing
Christian fixed it for the incoming 3.0.0
Sergey
On 18/04/14 18:30, samz2000 wrote:
The current CXF 2.6.13 or 2.7.10 - the blueprint xml files contain name space
handler from Apache Aries, which prevent other Blueprint implementation such
as Eclipse Gemini (https://www.eclipse.org/gemini/) to
The current CXF 2.6.13 or 2.7.10 - the blueprint xml files contain name space
handler from Apache Aries, which prevent other Blueprint implementation such
as Eclipse Gemini (https://www.eclipse.org/gemini/) to initialize CXF. I
think CXF should not locked itself in Apache Aries, just my 2 cents
.547215.n5.nabble.com/CXF-failed-to-publish-endpoints-in-Eclipse-4-2-2-OSGi-Jetty-8-1-14-and-Spring-3-0-7-environment-tp5742547p5743035.html
Sent from the cxf-dev mailing list archive at Nabble.com.
https://drive.google.com/file/d/0BwQeEkWPle9cYUZjbkpuVXJEQ00/edit?usp=sharing
To setup the enviornment in Eclipse,
a) you need to unzip the file, then import those projects into your Eclipse
workspace (use File | Import | Existing projects into workspace).
b) Then use 'jetty-config8b/tar
oid execute() throws MojoExecutionException {
> // add the generated source into compile source
> // do this step first to ensure the source folder will be added to
> the Eclipse classpath
> if (project != null && getGeneratedSourceRoot() != null) {
>
> proje
compile source
// do this step first to ensure the source folder will be added to
the Eclipse classpath
if (project != null && getGeneratedSourceRoot() != null) {
project.addCompileSourceRoot(getGeneratedSourceRoot().getAbsolutePath());
}
if (project
Hi all,
I see that whatever I set the value of cxf-codegen-plugin when
executing the wsdl2java goal, then in eclipse that folder get added as a
source folder.
Could someone please tell me how that it is achieved?
I would like to have the same behavior in the gwt-mavan-plugin.
Thank you
Forgot to mention this yesterday (and thanks to Sergey for pointing out that I
screwed up and forgot to commit/deploy some stuff in build utils):
I updated trunk to use the latest PMD maven plugin and all the new rulesets and
such. This also then requires the Eclipse users to update to the
; CXF-DOSGi. These are ok for pure Equinox and Felix frameworks.
> For Apache Karaf we will have a feature file in the next version that
> makes using DOSGi really simple there.
>
> I wonder if we should support an Eclipse Update Site for DOSGi to make
> it similarly easy to use in Ecli
Hi all,
we currently have the single bundle and multi bundle distributions for
CXF-DOSGi. These are ok for pure Equinox and Felix frameworks.
For Apache Karaf we will have a feature file in the next version that
makes using DOSGi really simple there.
I wonder if we should support an Eclipse
Hi all
When I run "mvn -Psetup.eclipse" and open the newly created eclipse workspace I
only see the "CXF Java Conventions" imported under Preferences -> Java -> Code
Style -> Formatter. I can manually add the "CleanUp" and "Organize Imports&quo
Hi Dan,
Could you review my updates in page
https://cwiki.apache.org/confluence/display/CXF/Connecting+Maven,+Eclipse,+Checkstyle,+and+PMD?
Just tried to make it more understandable and added information regarding
custom eclipse workspace location.
Regards,
Andrei.
Actually it's super easy in Eclipse, no need to jump all over the place and
run separate commands to get the WSDL built. Just list the WSDL list what
client you want to build it (Axis, Axis2, CXF) and what project you are
using. It builds it, and sticks the code right in the project. All
ava.lang.NoSuchMethodException:
javax.xml.bind.annotation.XmlElementRef.required()
at java.lang.Class.getDeclaredMethod(Class.java:1937)
at
com.sun.codemodel.TypedAnnotationWriter.invoke(TypedAnnotationWriter.java:112)
... 23 more
--
View this message in context:
http://cxf.547215.n5.nabble.com/
some less than ideal code
being committed.
In the last week or so, I went through and fixed all the warnings (over 2K of
them) in the CXF code so the CXF specific parts are now all warning free using
the default eclipse compiler settings.There are still warnings in
testutils, databinding/
On Thursday, July 28, 2011 9:42:03 PM Ray Ramos wrote:
> Daniel Kulp writes:
> > Is there more to that stack trace?There should be at least one more
> > "Caused by" at the end of that where the actual location of the NPE
> > should be found. Right now, I have no idea.
> >
> > In regards to r
Daniel Kulp writes:
>
>
> Is there more to that stack trace?There should be at least one more
> "Caused by" at the end of that where the actual location of the NPE should be
> found. Right now, I have no idea.
>
> In regards to removing the wsdlLocation attribute from , in
> that case,
the
service which needs the wsdl so it starts the service, etc
Dan
On Monday, July 18, 2011 5:57:38 PM Ray wrote:
> My environment is Eclipse Indigo with CXF 2.4.1 and Tomcat 6.0.26. The
> eclipse WS tool for generating servlet and java class files from a wsdl and
> xsd's
I changed the javaws:endpoing config to be just this
id="lexssearchretrieveporttype"
implementor="gov.usdoj.leisp.lexs.searchretrieve_3_1.ws
.LEXSSearchRetrievePortTypeImpl"
and Tomcat hangs until it times out.
My environment is Eclipse Indigo with CXF 2.4.1 and Tomcat 6.0.26. The eclipse
WS tool for generating servlet and java class files from a wsdl and xsd's
failed. The problem here, I think, is that the eclipse-ws tool is ignoring my
endorsed jars and trying to build using JAXS 2.1 instead of
Please disregard my previous email. I did not extract the entire download zip
file. After doing so Eclipse found everything.
Thank you
Hello:
I am using Eclipse Helios: Version: Helios Service Release 1 Build id:
20100917-0705.
Please see the attached jpeg file. I am using the
Hello:
I am using Eclipse Helios: Version: Helios Service Release 1 Build id:
20100917-0705.
Please see the attached jpeg file. I am using the instructions for installing
the CXF project facet found in Eclipse Help. Eclipse cannot find the
cxf-2.3.3.jar file that I have placed in the C
> it since I don't know how to "import" it. There is an Eclipse preferences
> export format, but it is not a .prefs file. Is one mechanism better than
> the other?
>
> On Sat, Dec 11, 2010 at 8:57 PM, Benson Margulies
wrote:
> > OK, I think it works. If you se
s the number of steps, please elaborate on what to do with it
since I don't know how to "import" it. There is an Eclipse preferences
export format, but it is not a .prefs file. Is one mechanism better than
the other?
On Sat, Dec 11, 2010 at 8:57 PM, Benson Margulies wrote:
> OK, I
OK, I think it works. If you set the profile m2eclipse, it will avoid
the custom-class PMD check, and you should get the same treatment we
get from the maven-eclipse-plugin.
On Sat, Dec 11, 2010 at 8:41 PM, Benson Margulies wrote:
> I see what the trick is here.
>
> When running in ecl
I see what the trick is here.
When running in eclipse, the existing scheme plays a trick to use set
of PMD rules that omits the custom rule, for the very reason you ran
into. Unfortunately for us, the auto-configuration tries to pick them
right back up, but that does not fly.
So, the question is
ave spaced out sufficient testing of
> this. I will look into the custom ruleset issue.
>
> --benson
>
>
> On Thu, Dec 9, 2010 at 11:44 AM, David Valeri wrote:
> > I've been using M2Eclipse in a workspace created by the Maven Eclipse
> > plug-in for some time
David,
I'm really sorry, I seem to have spaced out sufficient testing of
this. I will look into the custom ruleset issue.
--benson
On Thu, Dec 9, 2010 at 11:44 AM, David Valeri wrote:
> I've been using M2Eclipse in a workspace created by the Maven Eclipse
> plug-in for some
I've been using M2Eclipse in a workspace created by the Maven Eclipse
plug-in for some time now. This workspace had the PMD/checkstyle stuff
inserted into it by the Maven plug-in and I then deleted all of the projects
and imported just what I was working on using M2Eclipse. I saw th
The initial import. The 'rebuild' that happens when you change a dependency.
I recommend using a new, independent, eclipse install for this, and a
separate CXF tree. I expect you to find things to complain to me
about.
On Mon, Dec 6, 2010 at 1:59 PM, Daniel Kulp wrote:
> On Sunda
On Sunday 05 December 2010 9:48:46 am Benson Margulies wrote:
> Note that I've added some instructions to
>
> http://cxf.apache.org/setting-up-eclipse.html
>
> pointing to
>
> http://cxf.apache.org/cxf-m2eclipse.html
>
> which gives a procedure for loading
Note that I've added some instructions to
http://cxf.apache.org/setting-up-eclipse.html
pointing to
http://cxf.apache.org/cxf-m2eclipse.html
which gives a procedure for loading CXF into Eclipse with m2eclipse.
The biggest risk is Eclipse running out of permgen space. Some
activities are
have two Checkstyle sheets in the project properties, so I went
> > into my Eclipse configuration and saw that there appeared to be two
> > versions of the plugin installed. I uninstalled the older one, leaving
> > only the "Eclipse Checkstyle Plug-in" version 5.2.0.2010100720
On Wednesday 01 December 2010 6:01:14 am Dennis Sosnoski wrote:
> Tried this, even going with the default workspace this time, rather than
> the one I'd specified before. Still the same results, though.
>
> I did have two Checkstyle sheets in the project properties, so I went
Tried this, even going with the default workspace this time, rather than
the one I'd specified before. Still the same results, though.
I did have two Checkstyle sheets in the project properties, so I went
into my Eclipse configuration and saw that there appeared to be two
versions of the p
I'm running on Linux (OpenSUSE 11.3, 32bit). Eclipse shows the file
encoding as UTF-8 (inherited from container).
I've checked the hexdump of some of the files and confirmed there is no
0x character present. I did notice that the "//CHECKSTYLE:ON" line
in these files was r
r for import.
Occasionally, when importing the projects, Eclipse gets confused and doesn't
get everything setup correctly. Steps to resolve:
1) From the command line, re-run "mvn -Psetup.eclipse" to make sure everything
is regenerated properly.
2) Select all the projects in eclips
uot;just" the errors.
>>>
>>> Thanks,
>>>
>>> - Dennis
>>>
>>> On 11/27/2010 02:53 AM, Benson Margulies wrote:
>>>
>>>> Looks like you lack a subversion plugin to eclipse, which would
>>>> somehow prevent the
> of subclipse, deleted and re-imported the projects, and now I'm left
>> with "just" the errors.
>>
>> Thanks,
>>
>> - Dennis
>>
>> On 11/27/2010 02:53 AM, Benson Margulies wrote:
>>
>>> Looks like you lack a subv
leted and re-imported the projects, and now I'm left
> with "just" the errors.
>
> Thanks,
>
> - Dennis
>
> On 11/27/2010 02:53 AM, Benson Margulies wrote:
>> Looks like you lack a subversion plugin to eclipse, which would
>> somehow prevent th
enson Margulies wrote:
> Looks like you lack a subversion plugin to eclipse, which would
> somehow prevent the cs plugin from descending into your .svn
> directories.
>
> On Fri, Nov 26, 2010 at 5:10 AM, Dennis Sosnoski wrote:
>
>> I've followed the instructions at
>
Looks like you lack a subversion plugin to eclipse, which would
somehow prevent the cs plugin from descending into your .svn
directories.
On Fri, Nov 26, 2010 at 5:10 AM, Dennis Sosnoski wrote:
> I've followed the instructions at
> http://cxf.apache.org/setting-up-eclipse.html t
I've followed the instructions at
http://cxf.apache.org/setting-up-eclipse.html to create an Eclipse
project using the current trunk code, but Eclipse gives me a bunch of
Checkstyle errors as well as a bunch of warnings. Here's a
representative sampling of the Checkstyle errors (89 in
On Saturday 19 June 2010 10:31:19 am Glen Mazza wrote:
> Problem fixed. I upgraded to Maven 2.2.1 and also nuked my local Maven
> repository in case a file used in the build process was corrupted. But
> the NPE while building CXF-API still occurred (I'm not sure why I said
> "mvn -Pfastinstall"
e. If you
> run
> mvn -Psetup.eclipse a couple times, does it resolve itself?
>
> Dan
>
--
View this message in context:
http://old.nabble.com/NPE-setting-up-CXF-code-in-Eclipse-tp28617106p28934164.html
Sent from the cxf-dev mailing list archive at Nabble.com.
gt; eclipse:eclipse -e -Pfastinstall" or "mvn -Psetup.eclipse -e" to set up
> Eclipse (as explained here: http://cxf.apache.org/setting-up-eclipse.html)
> creates this error:
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException
> at
>
Hello, doing an svn update to get the latest CXF code, then mvn clean
-Pfastinstall is all fine. But subsequently running "mvn eclipse:clean
eclipse:eclipse -e -Pfastinstall" or "mvn -Psetup.eclipse -e" to set up
Eclipse (as explained here: http://cxf.apache.org/setting-up-e
Description ResourcePathLocationType
Wrong order for 'commonj.sdo.DataObject'
import. DataWriterImpl.java
/cxf-rt-databinding-sdo/src/main/java/org/apache/cxf/sdoline
33 Checkstyle Problem
Wrong order for 'commonj.sdo.DataObject'
import. HelloWorldDynamicTe
Works for me now, thanks
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com]
Sent: 31 August 2009 12:15
To: dev@cxf.apache.org
Subject: Re: New systests subprojetcs are not imported into Eclipse
That works for me. What version of Eclipse have you got?
You need to
That works for me. What version of Eclipse have you got?
You need to get rid of the .project and .classpath from the systests toplevel.
On Mon, Aug 31, 2009 at 6:33 AM, Sergey Beryozkin wrote:
> Hi
>
>
>
> After running 'mvn -Psetup.eclipse' on the trunk, I can see tha
Hi
After running 'mvn -Psetup.eclipse' on the trunk, I can see that all the
related files like .project/etc have been created in
systests/jaxrs, systests/aegis, systests/uncategorized, but no
projects can be imported from those subfolders.
Does it work for someone else ?
Cheers, Sergey
OK. This should now be fixed. I've updated the eclipse plugin config to
specify
none
which should turn off the plugins stupid/broken filtering that is causing the
aspect stuff to be removed.
Dan
On Wed August 26 2009 7:17:05 am Sergey Beryozkin wrote:
> I can't also run a
;src/main'. I'm wondering, what might've caused it ?
>
> The new maven eclipse plugin did this. It's kind of on purpose to make it
> closer match what surefire is doing when you run the tests. Surefire puts
> the tests first on the classpath before the src dirs
On Wed August 26 2009 6:14:24 am Sergey Beryozkin wrote:
> Hi
>
> After updating the source and rebuilding the workspace I can see 'src/test'
> being sorted before 'src/main'. I'm wondering, what might've caused it ?
The new maven eclipse plugin did
The jaxrs classpath is indeed ill in eclipse.
On Wed, Aug 26, 2009 at 7:17 AM, Sergey Beryozkin wrote:
> I can't also run a JAXRS test in Eclipse which depends on AOP aspects, for
> some reasons aspectj is not added to the list of libraries even though it's
> in the list
I can't also run a JAXRS test in Eclipse which depends on AOP aspects, for some reasons aspectj is not added to the list of
libraries even though it's in the list of dependencies in pom.xml...
cheers, Sergey
- Original Message -
From: "Sergey Beryozkin"
To:
Sen
Hi
After updating the source and rebuilding the workspace I can see 'src/test'
being sorted before 'src/main'. I'm wondering, what might've caused it ?
cheers, Sergey
> My collegue followed the instructions there and was rewarded with a
> nonfunctioning environment. I confess that I've had bad experience
> with the output of WTP in the past, so I'm not inclined to push him to
> try harder. Call me irresponsible ...
Push him to report the issues :)
--oh
rley wrote:
>> In my experience, trying to use 'incubator' materials out of Eclipse
>> is a recipe for incipient self-defenestration.
>
> 'Incubation' at Eclipse means that the project
> hasn't reached a 1.0 yet in terms of APIs
> and has not been th
> In my experience, trying to use 'incubator' materials out of Eclipse
> is a recipe for incipient self-defenestration.
'Incubation' at Eclipse means that the project
hasn't reached a 1.0 yet in terms of APIs
and has not been through an official release
review.
> No. We DID have an eclipse plugin, but it didn't do anything gui related. It
> literaly was just CXF and all the third party deps packaged into an eclipse
> plugin bundle thing so that could be put in the eclipse/plugins dir so that
> the STP tools could depend on it.
Yeah
That explains that.
In my experience, trying to use 'incubator' materials out of Eclipse
is a recipe for incipient self-defenestration. So if that's the best
there is, we're stuck. I do wonder about whether the JBoss gang has
something useful.
On Wed, Jul 15, 2009 at 1
On Tue July 14 2009 12:26:43 pm Oisin Hurley wrote:
> > I strongly remember that there was an entire eclipse plugin in our
> > tree back when I first showed up. I could be confabulating.
>
> I think you might be confabulating about that :)
No. We DID have an eclipse plugin
> http://cwiki.apache.org/CXF20DOC/cxf-tools-in-eclipse.html
>
> needs help.
Thanks
> I strongly remember that there was an entire eclipse plugin in our
> tree back when I first showed up. I could be confabulating.
I think you might be confabulating about that :)
--oh
http://cwiki.apache.org/CXF20DOC/cxf-tools-in-eclipse.html
needs help.
I strongly remember that there was an entire eclipse plugin in our
tree back when I first showed up. I could be confabulating.
On Tue, Jul 14, 2009 at 12:11 PM, Oisin Hurley wrote:
>> So, we got rid of our eclipse
> So, we got rid of our eclipse plugin because STP/WTP are supposed to
> be covering the ground, and now users here can't find anything working
> except betas on the bleeding edge, and our Confluence site is a
> 'someday' placeholder. Can someone tell me what's t
So, we got rid of our eclipse plugin because STP/WTP are supposed to
be covering the ground, and now users here can't find anything working
except betas on the bleeding edge, and our Confluence site is a
'someday' placeholder. Can someone tell me what's the current
situat
@cxf.apache.org
Cc: Willem Jiang
Subject: Re: a question when I run the JUnit test in eclipse.
On Sun June 7 2009 9:22:38 am Willem Jiang wrote:
> Hi,
>
> It may relate to your default maven repository directory "C:\Documents
> and Settings\jason\". It has space in the maven repository d
that would be appreciated. :-)
Dan
>
> Willem
>
> liucong wrote:
> > Hi all,
> >
> > I have encountered a question when I run the JUnit test in eclipse.
> >
> > I have set up my eclipse workspace(eclipse 3.4.1) following the orders
> > in h
Hi,
It may relate to your default maven repository directory "C:\Documents
and Settings\jason\". It has space in the maven repository directory,
which will cause the process starting error.
Willem
liucong wrote:
> Hi all,
>
> I have encountered a question when I run the JU
Hi all,
I have encountered a question when I run the JUnit test in eclipse.
I have set up my eclipse workspace(eclipse 3.4.1) following the orders
in http://cxf.apache.org/setting-up-eclipse.html.
Than I run a JUnit test
org.apache.cxf.systest.fault.IntFaultClientServerTest.java in
cxf-systests
to temporarily add a
fake test to the bottom of
org.apache.cxf.tools.wsdlto.jaxws.CodeGenTest
(in the wsdlto-test module) and debug it that way.
Dan
On Mon April 20 2009 4:12:52 am Glen Mazza wrote:
> Hello,
>
> I'm trying to run trunk's WSDLToJava.java in debug mode in Ec
Hello,
I'm trying to run trunk's WSDLToJava.java in debug mode in Eclipse. I've
imported the CXF project as described on our Eclipse page[1], in particular,
these steps here to import all the CXF subprojects:
# Select "Existing Projects into Workspace" and hit Nex
ns checkstyle/pmd, it DOESN'T wire their configuration
into the eclipse builders/plugins. Thus, you don't get the nice
checkstyle/pmd warnings while you edit code.
4) It also doesn't setup the warning levels and stuff that we kind of expect.
If you do the -Psetup.eclipse thing and
1 - 100 of 110 matches
Mail list logo
