You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2007/10/25 23:32:50 UTC
[jira] Created: (CXF-1138) Deploy source code to maven repo when
doing a build
Deploy source code to maven repo when doing a build
---------------------------------------------------
Key: CXF-1138
URL: https://issues.apache.org/jira/browse/CXF-1138
Project: CXF
Issue Type: Improvement
Components: Build system
Reporter: Christian Schneider
Fix For: 2.0.3
The public repository does not seem to contain the sources for cxf. When I started with cxf I built my project with maven but I could not debug into cxf as the sources where missing. What I did to solve the problem for me was simply to load the sources and do the maven build with:
mvn -Pfastinstall source:jar install
instead:
mvn -Pfastinstall
Deploying the build in this way would enable a novice user to start with a sample project and still be able to look into the code without any special effort.
So could you perhaps simply change the standard build procedure to include the sources?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1138) Deploy source code to maven repo when
doing a build
Posted by "Christian Schneider (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537745 ]
Christian Schneider commented on CXF-1138:
------------------------------------------
I just read the page about building that says how to do a build with deploy and that the sources will be delivered too. A quick look into the repo told me that the sources for 2.0.2 are there ... So it seems that I did something wrong. So I guess this issue is obsolete.
> Deploy source code to maven repo when doing a build
> ---------------------------------------------------
>
> Key: CXF-1138
> URL: https://issues.apache.org/jira/browse/CXF-1138
> Project: CXF
> Issue Type: Improvement
> Components: Build system
> Reporter: Christian Schneider
> Fix For: 2.0.3
>
>
> The public repository does not seem to contain the sources for cxf. When I started with cxf I built my project with maven but I could not debug into cxf as the sources where missing. What I did to solve the problem for me was simply to load the sources and do the maven build with:
> mvn -Pfastinstall source:jar install
> instead:
> mvn -Pfastinstall
> Deploying the build in this way would enable a novice user to start with a sample project and still be able to look into the code without any special effort.
> So could you perhaps simply change the standard build procedure to include the sources?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (CXF-1138) Deploy source code to maven repo when
doing a build
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp closed CXF-1138.
----------------------------
Resolution: Invalid
Fix Version/s: (was: 2.0.3)
Invalid
We have been deploying source jars (and javadoc jars) for all the deploys.
> Deploy source code to maven repo when doing a build
> ---------------------------------------------------
>
> Key: CXF-1138
> URL: https://issues.apache.org/jira/browse/CXF-1138
> Project: CXF
> Issue Type: Improvement
> Components: Build system
> Reporter: Christian Schneider
> Fix For: Invalid
>
>
> The public repository does not seem to contain the sources for cxf. When I started with cxf I built my project with maven but I could not debug into cxf as the sources where missing. What I did to solve the problem for me was simply to load the sources and do the maven build with:
> mvn -Pfastinstall source:jar install
> instead:
> mvn -Pfastinstall
> Deploying the build in this way would enable a novice user to start with a sample project and still be able to look into the code without any special effort.
> So could you perhaps simply change the standard build procedure to include the sources?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.